Skip to main content
Glama

execution_economics

Read-onlyIdempotent

Read your settled trial revenue and spend plus explicitly self-reported cost coverage. Reported margin is not real profit; missing cost must not be treated as zero.

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": "execution_economics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-obvious interpretation guidance: reported margin is not real profit and missing cost must not be treated as zero. That is useful behavioral context beyond the structured fields, though it says nothing about freshness, currency, or granularity of the figures.

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 primary data statement front-loaded and the caveats following. Jargon such as 'settled trial' and 'cost coverage' is used without definition, which costs it a point.

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 zero-parameter read tool with no output schema, the description should at least sketch the shape of the returned figures; instead the agent must discover the response format at call time. The interpretive caveats are valuable but leave terms like 'settled' and 'cost coverage' undefined.

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, so the schema has nothing to document and the baseline is 4. The description correctly implies a no-argument, account-scoped read with no filtering options.

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 (Read) and a specific resource (settled trial revenue and spend, plus self-reported cost coverage), which disambiguates the vague tool name 'execution_economics'. It does not differentiate from any sibling, but no sibling in the provided list appears to be an economics/metrics tool, so there is nothing to contrast against.

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?

Usage is only implied: an agent infers it should call this when it needs revenue/spend/cost figures. There is no explicit when-to-use or when-not-to-use statement, and no named alternative for related data.

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