Skip to main content
Glama

AgentSupply

Request a service

submit_request

Request any service (pilot services, volume access to live tools, or 'custom' for anything not listed). Describe the problem, volume, frequency and what you would pay. A human reviews every request. Returns request_id, status_token and status_url. Nothing is charged.

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": {
      "problem": "<problem>"
    },
    "name": "submit_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoShort title of the need.
problemYesWhat you need and why. Include the task your agent could not complete.
urgencyNo
currencyNoEUR
operatorNoOrganisation operating the agent (self-reported).
frequencyNoOne-off job or recurring need.
agent_nameNoName of the requesting agent (self-reported).
service_idNoCatalog service id, or 'custom' for anything not listed.custom
max_latencyNoRequired response time, e.g. '<5s', '<1h', '<24h'.
callback_urlNoOptional https URL for future status notifications (not yet active in the pilot).
requirementsNoConcrete requirements: coverage, accuracy, format, constraints.
contact_emailNoEmail for our reply (recommended – otherwise poll the status URL).
example_inputNoExample of what you would send us.
pricing_modelNoPreferred pricing model.
agent_card_urlNoURL of your A2A Agent Card, if any (https).
agent_platformNoFramework/runtime/model provider (self-reported).
interface_prefNoHow you want to integrate/receive results.
monthly_budgetNoMonthly budget for recurring needs.
monthly_volumeNoExpected number of units/requests per month.
one_off_budgetNoTotal budget for a one-off job.
requester_typeNoWho is sending this request.
expected_outputNoExample or schema of what you expect back.
payment_methodsNoPayment methods you can use.
max_price_per_unitNoMaximum price you would pay per unit/request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), the description adds meaningful behavior: a human reviews every submission, nothing is charged, and it returns request_id, status_token and status_url. The non-idempotent nature (each call creates a new reviewed request) is implied rather than stated, which keeps it from a 5.

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

Conciseness5/5

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

Four short sentences, front-loaded with scope, then what to supply, then the review process, then the return values. No redundant restatement of the schema and no filler.

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

Completeness4/5

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

For a 24-parameter, single-required-field submission tool with no output schema, the description covers the essentials: what to include, that a human reviews it, that it is free, and exactly what comes back. The remaining gap is follow-up guidance — it names status_token/status_url but never points at get_request_status as the polling sibling.

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

Parameters4/5

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

Schema coverage is already 92%, so the baseline is 3; the description goes further by prioritizing the fields that actually drive matching — problem, volume, frequency and price — which helps an agent triage 24 optional parameters down to the ones that matter. It does not explain the semantics of the enum-heavy fields (service_id, interface_pref, pricing_model), so it adds value but not full coverage.

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+resource ('Request any service') and enumerates scope: pilot services, volume access to live tools, or 'custom' for anything unlisted. This clearly separates it from catalog/read siblings like list_services, get_service or check_eu_vat, though it never names those siblings explicitly.

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

Usage Guidelines4/5

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

It gives clear context for when to submit: anything not covered by the listed catalog, with 'custom' as the fallback, and it instructs the agent what to include (problem, volume, frequency, willingness to pay). It stops short of saying 'check get_service/list_services first' or when not to submit, so no explicit alternatives are routed.

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