Skip to main content
Glama
Sign In

RiskDiff

by com.riskdiff
OverviewDiscussionsAdmin

List Company Diffs

list_company_diffs

List available year-over-year diffs for a specific company

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": {
      "ticker": "<ticker>"
    },
    "name": "list_company_diffs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g. "AAPL", "TSLA")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. "List available" weakly implies a read-only enumeration, but it says nothing about permissions, scope of "available" (how many years back), pagination, or ordering — all material for a tool an agent will chain into.

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?

One sentence, front-loaded with the verb and resource, zero filler. It is efficient but so terse that no secondary detail (result shape, chaining with get_company_diff) earns a place, which slightly under-serves the reader.

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?

With one parameter, no annotations, and no output schema, the description is minimally adequate: an agent knows what to pass and roughly what it gets. It leaves open what a "diff" entry looks like and how to use the results, which the absent output schema would otherwise have covered.

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?

The single parameter is fully documented in the schema (100% coverage) with an example. The description adds only the loose mapping of "specific company" to ticker, which the schema already conveys; baseline 3 applies when the schema does the work.

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?

Specific verb ("List") plus resource ("year-over-year diffs") scoped to a company, which is more informative than the bare name. It doesn't explicitly distinguish itself from the sibling get_company_diff, so an agent must infer that this is the enumeration step versus the retrieval step.

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: "list available" suggests calling this first to discover what diffs exist before fetching one with get_company_diff. No explicit when-to-use, when-not-to-use, or prerequisite (e.g., ticker must be a known company) is stated.

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

All RiskDiff toolsInspect
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