Submit user feedback for model improvement loop.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| rating | Yes | ||
| lead_id | Yes | ||
| campaign_id | No | ||
| access_token | No | ||
| tenant_api_key | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It only implies a write action but omits side effects, authentication requirements, idempotency, or response behavior. This is insufficient for an agent to anticipate impact.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence that front-loads the verb and is appropriately brief. It is not padded, but it sacrifices potentially valuable context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given six parameters, including auth fields, and an output schema, the description is too sparse. It doesn't explain how feedback relates to leads/campaigns, what ratings mean, or the expected workflow, leaving critical ambiguities.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the description mentions no parameters. With six parameters, including sensitive ones like access_token and tenant_api_key, the agent receives no help understanding what to pass. The description entirely fails to compensate for the schema's lack of documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Submit user feedback' and its purpose ('for model improvement loop'). It uses a specific verb and resource, though it doesn't explicitly differentiate from sibling tools beyond the name, which is distinct enough.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool instead of alternatives. It does not mention prerequisites, context (e.g., needing lead_id or rating), or how it relates to sibling tools like get_lead or run_campaign.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: cost estimation, bulk lead export, campaign status, single lead retrieval, vertical listing, campaign creation, and feedback submission. No two tools have overlapping purposes; even get_campaign and get_lead are clearly separated by campaign vs. lead granularity.
All tool names follow a consistent verb_noun pattern in snake_case (estimate_cost, export_leads, get_campaign, get_lead, list_verticals, run_campaign, submit_feedback). This is a uniform and predictable naming convention.
The server has 7 tools, which is well within the ideal 3–15 range. Each tool serves a clear function in the campaign lifecycle without redundancy, making the count appropriate for the domain.
The server covers campaign creation (run_campaign), reading campaign status (get_campaign), lead access (get_lead, export_leads), cost estimation, and feedback. However, it lacks list_campaigns, update_campaign, and delete_campaign, which are notable gaps for managing multiple campaigns. The core workflow is usable but not a full CRUD surface.