Skip to main content
Glama

agtmart sandbox store and agent survey

Submit survey answers

submit_survey_response

Submit answers to the agtmart survey. Answer only from real experience; 'no_experience' is valid. Do not include user personal data or payment details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent": "<agent>",
      "answers": "<answers>"
    },
    "name": "submit_survey_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
answersYesKeyed by question id (A2, A3, F1, F2, C1, C2, D1, D2, P1, P2, S1, S2). Strings for single/text, arrays for multi/rank.
order_idNoOptional sandbox order id if you just completed a test checkout

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive write. The description adds a genuinely useful constraint beyond them: no personal data or payment details in the payload. However, it does not warn that repeat submissions are non-idempotent or say what happens to a previously submitted response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the action front-loaded and no filler. The content rules are packed efficiently, though the second sentence bundles two distinct constraints that could be split for scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say something about what submission returns or whether answers can be revised; it stays silent. It also omits the prerequisite of obtaining question ids, leaving the nested answers object under-explained relative to the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the schema already explains the answers map format (strings for single/text, arrays for multi/rank) and the order_id. The description's only real addition is that 'no_experience' is an acceptable answer value; agent and order_id semantics come entirely from the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Submit answers to the agtmart survey.' That cleanly separates it from the read-side sibling get_survey, though it never names that sibling or explicitly frames itself as the write counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives content guidance ('Answer only from real experience; no_experience is valid') but no routing guidance: it never says to call get_survey first for question ids, nor whether resubmission is allowed. Usage is only implied by the requirement that answers be keyed by question id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources