Skip to main content
Glama

Stocks On Chain

Look up a contract address

get_contract
Read-onlyIdempotent

What this site holds about one address, in two independent halves. listings says what the token IS - the stock, its company, the issuer and the chain - and is present whenever the address is a listing we track. matches says what the CODE at the address is: its runtime bytecode hash, the implementation behind it if it is a proxy, and how many other addresses we track run byte-identical code; it is present only where we have read the code. The code half is reproducible: fetch eth_getCode and take its keccak256 and you get the same hash. Either half can be empty and both can be present; an address we hold nothing about returns found: false, which is an answer rather than an error. This never says an address is safe, genuine or correct, and there is no field that could: check it against the issuer before you act on it.

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": {
      "address": "<address>"
    },
    "name": "get_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain slug, for example ethereum or robinhood-chain. Optional. Omit it to find the address on every chain we hold it.
addressYesThe contract address, in any case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses several important behaviors: listings and matches can be independently present or empty, a missing address returns `found: false` rather than an error, and the code half is reproducible via `eth_getCode` plus keccak256. It also explicitly warns that the tool never asserts safety or genuineness, which is valuable behavioral context for interpreting results.

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 front-loaded with the core concept and then structured into clear statements about `listings`, `matches`, reproducibility, empty-result behavior, and safety limits. Despite being fairly long, each sentence conveys distinct and useful information, and the backticked field names improve scanability.

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

Completeness5/5

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

There is no output schema, so the description must explain returned data, and it does so thoroughly: it names the two halves, describes their contents and presence conditions, and explains the `found: false` case. For a read-only, two-parameter lookup tool, this is complete enough for an agent to invoke and interpret the result correctly.

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 coverage is 100%, so both `address` and `chain` are already documented in the input schema. The description adds some conceptual meaning to `address` by explaining that it may represent a tracked listing, readable code, or both, but it does not add syntax, formatting, or chain-specific parameter behavior beyond the schema. The baseline of 3 is appropriate when the schema carries the parameter documentation.

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 opens with a specific scope: what the site holds about one address, split into `listings` and `matches`. It clearly distinguishes the two independent halves and what each represents, so an agent can understand the tool's purpose without opening another schema. Sibling tools are not explicitly named, but the address-level lookup purpose is unmistakable.

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?

The description gives some contextual guidance, such as omitting `chain` to search every chain and checking results against the issuer before acting. However, it does not explicitly say when to choose this tool over related siblings like `get_stock` or `search_stocks`, nor does it state when not to use it. Usage is therefore implied rather than explicitly guided.

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