Parrot (parrot.markets)

Occasion brief

brief

Read-only

One call, a row per listed word: settled n/y/rate/l10, transcript th/tn, p. By event, appearance, or entity(+date). <=3.2 KB; offset pages the rest.

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

Input Schema

Name	Required	Description	Default
`date`	No
`event`	No
`limit`	No
`entity`	No
`fields`	No
`format`	No
`offset`	No
`symbol`	No
`markets`	No
`appearance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

C2.3/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world operation. The description adds useful behavioral constraints beyond annotations: a maximum response size of 3.2 KB and offset-based pagination for the remainder. It still omits defaults, error behavior, and what happens when no filters are supplied.

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

Conciseness3/5

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

The description is compact and front-loaded with the output shape, but its telegraphic abbreviations ('settled n/y/rate/l10', 'transcript th/tn, p') make it difficult to parse. There is no wasted prose, but concision comes at the cost of clarity.

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

Completeness2/5

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

For a 10-parameter tool with no output schema and no schema descriptions, the definition is too sparse to be complete. It omits default behavior, how filters combine, what the returned columns mean in plain language, and what the output looks like in each format.

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

Parameters2/5

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

With 0% schema description coverage across 10 parameters, the description must carry the explanatory burden, but it only loosely mentions event, appearance, entity(+date), and offset. It says nothing about limit, format, symbol, markets, or precise meanings for fields, leaving most parameters undocumented.

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

Purpose2/5

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

The description never clearly states what a 'brief' is or what action the tool performs; it mostly lists terse output columns like 'settled n/y/rate/l10' and 'transcript th/tn'. It alludes to filtering by event, appearance, or entity(+date), but an agent cannot confidently distinguish this tool's purpose from siblings such as 'word' or 'entity'.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives like 'search', 'word', or 'entity'. The phrase 'By event, appearance, or entity(+date)' hints at filter modes, but it does not state conditions for choosing this tool or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Parrot (parrot.markets) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?