Skip to main content
Glama

Get Startup Signal

get_startup_signal
Read-onlyIdempotent

Get engineering momentum signal for a specific startup.

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": {
      "startup": "<startup>"
    },
    "name": "get_startup_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
startupYesName of the tracked startup to get the engineering momentum signal for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / startup / description
      Added value: +"Name of the tracked startup to get the engineering momentum signal for."
    • addedInput schema / properties / startup / examples
      Added value: +[
      +  "vercel",
      +  "supabase"
      +]
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds nothing beyond that: no mention of what the signal contains, how it is computed, staleness, or rate limits, so it contributes no behavioral context of its own.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of underspecifying the payload.

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?

There is no output schema, so the description is the only place the return value could be characterized — yet 'engineering momentum signal' is left opaque. For a tool whose entire value is the shape of its output, that is a significant gap.

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?

With a single parameter at 100% schema coverage, the schema already documents 'startup' including examples (vercel, supabase). The description only restates that the parameter scopes the signal to one startup, so baseline 3 applies.

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 verb 'Get' and the resource 'engineering momentum signal' are named, and the scope is limited to 'a specific startup', which separates it from the list_/search_ siblings. However, 'signal' is never defined, so an agent cannot tell what data it actually returns.

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?

There is no guidance on when to call this instead of search_startups or the list_ tools, and no stated prerequisites such as whether the startup must already be tracked. The agent must infer selection from the name alone.

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