Skip to main content
Glama

Report outcome

report_outcome

Records how the contact with a revealed business went. wrong_number and closed give the credit back (within 14 days, up to 10% of what was revealed that month) and send the business back to research. Use note 'do not contact' when a business asks not to be written to again.

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": {
      "code": "<code>",
      "outcome": "<outcome>"
    },
    "name": "report_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
noteNo
contactNoThe number or email used; defaults to the main contact
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare mutating, non-destructive, non-idempotent, closed-world. The description adds real business consequences the annotations cannot convey: wrong_number and closed reverse credit within 14 days and capped at 10% of that month's reveals, and route the business back to research. It omits whether re-reporting the same code double-counts, which matters given idempotentHint=false.

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 sentences, purpose front-loaded, with the credit-reversal rule and the note convention each stated once. Dense but no wasted clause; the parenthetical cap is necessary detail, not padding.

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?

For a mutation tool with no output schema, the description covers the downstream side effects well but leaves a required identifier (`code`: min 6, max 32) unexplained and says nothing about the caller-visible result. An agent knows the consequences of two outcomes but not how to reliably construct the required input.

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 25% — only `contact` is described, so the description must compensate. It does add meaning for two outcome values (wrong_number, closed) and for `note`, but leaves `code` (a required, format-constrained string) and the remaining outcome values (worked, no_answer, not_whatsapp) undefined.

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?

States a specific verb and resource: it records the outcome of a contact with a revealed business. The credit-reversal behavior for wrong_number/closed further pins down what the record drives, though it doesn't explicitly contrast with siblings like reveal_contacts or get_business.

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?

Gives one concrete when-to-use rule: use note 'do not contact' when a business asks not to be written to again. It does not say when this tool should be called relative to the outcome lifecycle (e.g., only after reveal_contacts) or which outcome value fits which situation, so usage is only partially implied.

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