Quantral Stock Sentiment

US patents

get_company_patents

Read-onlyIdempotent

Returns a company's most recent US patent grants from the USPTO, newest first, each with the patent number, title and grant date. Patents are shown for context only: they are not part of the Quantral score and are not investment advice.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Number of grants to return (1-50, default 10).
`ticker`	Yes	Ticker symbol, for example NVDA.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the upstream source (USPTO), newest-first ordering, and the exact fields returned per grant. It omits any mention of data lag or that only US grants are covered beyond the title, which keeps it below a 5.

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?

Two sentences, front-loaded with what is returned and immediately followed by the scope caveat. Nothing is redundant or padding; every clause carries information.

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 simple two-parameter read tool with full annotations and no output schema, the description is near-complete: it enumerates the returned fields so the agent knows what to expect. Minor gaps remain around data freshness and ticker coverage, which would matter for interpreting results.

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%, so both parameters are already documented, including the 1-50 range and default of 10. The description only reinforces that results are the most recent, newest first, adding no format or usage detail beyond the schema. Baseline 3 applies.

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?

A specific verb and resource ("Returns a company's most recent US patent grants from the USPTO") plus the ordering and returned fields. It clearly separates this from data tools like the score by noting patents are context only, though it never names an alternative tool outright.

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 implied rather than stated: an agent can infer this is for looking up a company's recent patent activity. The one explicit boundary is negative — patents are not part of the Quantral score and are not investment advice — which functions as a mild when-not. There is no guidance on prerequisites, coverage windows, or when to prefer a different tool.

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

All Quantral Stock Sentiment 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?