Skip to main content
Glama

ADS Beast

lead_outcome_contract

Read-only

Return the field names and outcome values that push_lead_outcomes accepts, as the server currently defines them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lead_outcome_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description still adds meaningful behavior by qualifying the answer as 'as the server currently defines them', signaling the contract is server-side and potentially unstable, so results should not be cached or hard-coded. It stops short of describing the shape of the returned payload.

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?

A single front-loaded sentence with no hedging or filler. The key noun (the accepted fields) arrives immediately, and the qualifier about server-defined state is placed where it reads naturally.

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 zero-argument, no-output-schema introspection tool, the description conveys both what is returned (field names and outcome values) and that it reflects live server definitions. Only the rough shape of the return value (names only vs. names with types/allowed values) is left unstated.

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?

The tool takes zero parameters and the description correctly promises no filtering or selection arguments, so nothing is left ambiguous. No parameter-level semantics are needed here.

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 specific verb (Return) and a precise resource (the field names and outcome values accepted by push_lead_outcomes), and names the sibling it serves. An agent can distinguish this introspection call from the sibling push_lead_outcomes without opening either schema.

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?

The link to push_lead_outcomes makes the pre-flight discovery use case strongly implied, but the description never states explicitly 'call this before push_lead_outcomes' nor gives any when-not condition. Usage is inferable rather than instructed.

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.