mcp-server

Get Contract Events

get-contract-events

[Auth Required] Paginated events for a contract the agent has access to.

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": {
      "contract_id": "<contract_id>"
    },
    "name": "get-contract-events"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number
`perPage`	No	Results per page
`parent_id`	No	Filter by parent event id (load children/comments of a task)
`contract_id`	Yes	Contract ID

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 2, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations are empty, so description carries burden. Adds 'Auth Required' and 'paginated' but lacks details on ordering, rate limits, or read-only nature. Does not contradict annotations.

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?

Single sentence with key qualifier front-loaded. No unnecessary words, but could be slightly more structured with explicit separation of auth note and function.

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?

Lacks output schema and annotation context. Description does not explain what data is returned (fields, sorting) or any additional behavioral notes for a read operation. Minimal completeness given tool complexity.

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 parameters are documented in schema. Description only confirms pagination but adds no new semantic meaning beyond schema.

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?

Clear verb 'get' and resource 'contract events', specifies scope 'the agent has access to'. Distinguishes from similar siblings like 'get-event' for single event, but does not explicitly differentiate.

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?

Provides no guidance on when to use vs alternatives like 'get-event' or 'get-event-children'. No when-not-to-use instructions. Only mentions authentication requirement.

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

All mcp-server 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.