Skip to main content
Glama
Sign In

filings

by global.rootz.origin
OverviewDiscussionsAdmin

origin_company

Look up a US public company by ticker. SEC-verified, ~200 tokens. Use this FIRST for any company query.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesStock ticker (e.g. AAPL, MSFT, WAVX) or CIK number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses the data source (SEC-verified) and token cost (~200 tokens). However, it does not mention potential errors, rate limits, or the exact nature of the response (e.g., read-only). A score of 4 is appropriate as it provides key behavioral traits without being exhaustive.

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?

The description is extremely concise with two sentences. The first sentence states the core purpose, and the second provides usage guidance and key attributes. No unnecessary words.

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?

Given the tool's simplicity (single parameter, no output schema), the description is adequate but lacks details on what the lookup returns (e.g., company name, sector). Since no output schema is provided, the description could be more complete by hinting at typical output fields.

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 description coverage is 100% with a clear description of the 'ticker' parameter. The tool description adds no additional semantic information beyond what the schema already provides, so baseline score of 3 is appropriate.

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?

The description clearly states the tool's function: 'Look up a US public company by ticker.' It distinguishes itself from siblings by being the primary company lookup tool, as indicated by 'Use this FIRST for any company query.'

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

Usage Guidelines5/5

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

Description explicitly advises to 'Use this FIRST for any company query,' providing clear usage context among sibling tools. It also mentions the tool is 'SEC-verified' and costs '~200 tokens,' helping the agent assess reliability and cost.

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

All filings 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