Skip to main content
Glama
Sign In
openpitch-mcp

openpitch-mcp

by Avierovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_events

Read-onlyIdempotent

Retrieve filtered event streams for AI startup metrics, including funding and ARR updates, with filters by type, date, company, and confidence.

Instructions

Filtered event stream (the push layer).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
sinceNo
company_idNo
min_confidenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating safe read operations. The description adds no behavioral info beyond stating 'push layer', which is undefined and does not enhance transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely short (4 words), but this brevity sacrifices clarity and completeness. While concise, it fails to earn its place by providing necessary information.

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

Completeness1/5

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

With no output schema and zero schema description coverage, the description is grossly insufficient. It does not explain return values, pagination, or behavior, leaving major gaps for a tool with 4 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no explanation of any parameter. Four parameters (type, since, company_id, min_confidence) are entirely undocumented, leaving the agent without meaning for filtering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Filtered event stream (the push layer)' indicates it returns events with filtering capability, but it is vague and uses jargon ('push layer') without explanation. It somewhat distinguishes from sibling tools like search or get_company by focusing on events, but lacks specificity.

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?

No guidance on when to use this tool versus alternatives like search or what_moved. The description does not mention any context or exclusions.

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

Deploy Server

Other Tools