Skip to main content
Glama

Duplicate group report module with pytest tests

submit_duplicate_group_report
Idempotent

Produce a standard-library Python module that groups records sharing a key field, plus pytest tests. Choose this when you need each repeated key value reported with its count and the positions of its members. Do not choose this to remove duplicates (use record-deduplication) or to match near-duplicates. Example requests: Write a Python module that groups records by a key field and reports duplicated values, with tests. | I need to know which key values occur more than once, with counts and positions. | Generate a duplicate-group report module and prove it with pytest.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_duplicate_group_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that output is standard-library only and that the template fixes the behavior and is self-verified by its own tests, but it never mentions that this is a priced/async job requiring quote authorization, which is the most consequential behavior for an agent.

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?

Purpose, selection criteria, and exclusions are front-loaded and tightly worded. The three example requests are slightly redundant with the preceding sentences, costing a little economy without harming clarity.

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?

An output schema exists so return values need no explanation, and the description covers what is produced and when to choose it. The notable gap is the quote/price authorization flow, which the agent must infer from the schema alone for a submission-style tool.

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 75% and each property (template, module_name, function_name, quote_id, authorized_by, accepted_price) already carries its own description. The description reinforces the grouping semantics but adds no format, constraint, or ordering detail beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

States a concrete verb and artifact ('Produce a standard-library Python module that groups records sharing a key field, plus pytest tests'), which is immediately distinguishable from siblings like submit_record_deduplication or submit_key_normalisation.

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

Usage Guidelines5/5

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

Explicit positive condition ('Choose this when you need each repeated key value reported with its count and the positions of its members') and explicit exclusions with the named alternative ('Do not choose this to remove duplicates (use record-deduplication) or to match near-duplicates').

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