Agent Tool Card Builder — Feature Deep Dive¶
What It Is¶
A structured form + AI generator that creates marketplace-ready listing cards for AI tools and agents. Partners fill in tool metadata (name, category, AWS services, protocols), and Vellocity's AI generates a complete, compliance-checked card suitable for AWS Marketplace or MCP/OpenAPI distribution.
Where It Lives¶
- Workflow Path: Unified Workflow → Listing Marketing domain → Step 1: "Create Your Listing"
- Actions:
agent_tool_card(listing card only),agent_resource_pack(full GTM bundle with MCP/OpenAPI schemas) - URL: Uses the generic
/dashboard/user/openai/generateendpoint
Form Fields Captured¶
| Field | Type | Details |
|---|---|---|
| Tool Name | Text input | Name of the AI tool/agent |
| Partner Company | Text input | Company behind the tool |
| Tool Description | Textarea | Capabilities and purpose |
| Category | Dropdown | AI Agent, AI Tool, AI Framework, AI Model Service |
| AWS Services | Multi-select + quick buttons | Bedrock, Lambda, SageMaker, S3, etc. |
| Supported Protocols | Checkboxes (resource_bundle only) | MCP, OpenAPI, REST, gRPC |
| Pricing Model | Dropdown | Usage-based, Subscription, Free Tier, BYOL |
What Gets Generated (AgentToolCardSchema)¶
The AI (Claude 3 Sonnet via Bedrock) generates a structured JSON schema with these sections:
tool_metadata¶
name, slug, tagline, description, category, subcategory, partner_company, logo_url, aws_services[], pricing_model, schema_version
capabilities[]¶
Array of capabilities, each with: name, description, type (core|optional|premium), input_type, output_type, input_schema, output_schema
integration¶
deployment_model (saas|container|lambda|marketplace_ami), auth_methods[], input_formats[], output_formats[], protocols[], sdk_languages[], aws_integrations[]
gtm_content¶
short_description(≤80 chars, AWS Marketplace constraint)full_description(≤2000 chars)highlights(3-5 bullet points)use_cases[],getting_started,support_url,documentation_url,demo_url
agent_schema (for MCP/OpenAPI export)¶
tool_definition[] (MCP-compatible), input_schema, output_schema, example_invocations[]
compliance¶
overall_score (0-100), overall_status, checks[]
Compliance Engine (9 Automated Checks)¶
| Check | Severity | Rule |
|---|---|---|
| short_description_length | Error | ≤80 chars |
| full_description_length | Error | ≤2000 chars |
| highlights_count | Warning | 3-5 bullets |
| capabilities_defined | Error | At least 1 |
| use_cases_present | Warning | At least 2 |
| getting_started | Warning | Must exist |
| agent_schema_defined | Info | Tool definitions present |
| aws_services_referenced | Warning | AWS services mentioned |
| example_invocations | Info | Example calls provided |
Scoring: 100-point scale → passed | needs_review | failed
Export Formats¶
- MCP Tool Definition —
schema_version: 2025-11-25, server_info, tools[] with inputSchema - OpenAPI 3.1.0 — paths with operations per capability
- Markdown Preview — human-readable card format
Credits¶
tool_card: 25 creditsagent_schema: 20 creditsresource_bundle: 40 credits
Key Files¶
| File | Purpose |
|---|---|
resources/views/default/panel/user/unified-workflow/components/agent-tool-card-fields.blade.php |
Form UI |
app/Models/AgentToolCard.php |
DB model (table: agent_tool_cards) |
app/Extensions/AiPresentation/System/Schema/AgentToolCardSchema.php |
Schema structure + exports |
app/Extensions/ContentManager/System/Services/Capabilities/AgentToolCardCapability.php |
AI generation + compliance |
database/migrations/2026_02_24_000001_create_agent_tool_cards_table.php |
DB migration |
Implementation Status¶
Fully Built: - Form component with all fields - AI generation via Bedrock (Claude 3 Sonnet) - Compliance validation (9 checks, scoring) - Schema serialization to MCP/OpenAPI/Markdown - Database storage with user/team ownership - Integration into Listing Marketing workflow
Gaps / Next Steps: - No dedicated detail/edit page for viewing saved tool cards (only in-workflow generation) - No marketplace publishing UI (schema exports exist but no push-to-marketplace flow) - No card gallery/library view to browse previously generated cards - Consider adding a "Preview as Marketplace Listing" live preview (similar to Content Optimizer's live preview) - The landing page mockup we created shows this feature — could link the "See it in action" CTA to the workflow
Why This Matters¶
This is a differentiating feature: Vellocity doesn't just help partners write listing copy — it generates structured, machine-readable tool definitions (MCP/OpenAPI) that make partner tools discoverable and integrable by AI agents. This positions Vellocity at the intersection of GTM and the emerging agent ecosystem.