Skip to main content
Glama

PitchSpark: Pre-Seed & Seed Startup Pitches

Check that PitchSpark pitch search is up

pitchspark_get_health_v1
Read-onlyIdempotent

Check that PitchSpark's startup pitch service is answering before relying on it, and which API version it speaks. Use when: you only need to know whether the service is available. Do not use for: finding startups or reading pitches; it returns no pitch data. Returns {"status":"ok","version":"1.0"}. No API key is needed, even when the server requires one for the other tools. It uses none of the daily pitch allowance and none of the other tools' per-minute limits: health has its own per-connection call limit, and the call is logged. Read-only: does not change your data or any pitch content. Requests are logged, and each pitch returned is counted as a view. Opening a returned pitch link can add one spark to the pitch's public spark count (once per viewer, updated hourly). Pitch search is pitchspark_search_pitches_v1.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed (isError true).
statusNo
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "anyOf": [
      +    {
      +      "required": [
      +        "status",
      +        "version"
      +      ]
      +    },
      +    {
      +      "required": [
      +        "error"
      +      ]
      +    }
      +  ],
      +  "properties": {
      +    "error": {
      +      "additionalProperties": false,
      +      "description": "Present only when the call failed (isError true).",
      +      "properties": {
      +        "category": {
      +          "description": "The error class.",
      +          "enum": [
      +            "RATE_LIMITED",
      +            "QUOTA_EXCEEDED",
      +            "UNAUTHORIZED",
      +            "FORBIDDEN",
      +            "VALIDATION_ERROR",
      +            "NOT_FOUND",
      +            "CONFLICT",
      +            "UNKNOWN_TOOL",
      +            "INTERNAL"
      +          ],
      +          "type": "string"
      +        },
      +        "code": {
      +          "description": "Machine-readable error code, e.g. RATE_LIMITED, UNAUTHORIZED, FORBIDDEN, INVALID_ARGUMENT, NOT_FOUND, CONFLICT, PITCH_LIMIT_REACHED, INTERNAL.",
      +          "type": "string"
      +        },
      +        "message": {
      +          "description": "A short human-readable explanation, safe to show the user. Never a stack trace.",
      +          "type": "string"
      +        },
      +        "retry_after_seconds": {
      +          "description": "Seconds to wait before retrying, when waiting helps.",
      +          "minimum": 0,
      +          "type": "integer"
      +        },
      +        "retryable": {
      +          "description": "true when the same call can succeed later without changes.",
      +          "type": "boolean"
      +        }
      +      },
      +      "required": [
      +        "code",
      +        "message"
      +      ],
      +      "type": "object"
      +    },
      +    "status": {
      +      "enum": [
      +        "ok"
      +      ],
      +      "type": "string"
      +    },
      +    "version": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, and destructiveHint already declared, the description still adds real value: no API key required even when the server mandates one elsewhere, no consumption of the daily pitch allowance, and a separate per-connection call limit. The trailing sentences about pitches returned being counted as views and spark counts are inapplicable to a tool that returns no pitches, which weakens the otherwise strong disclosure.

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?

The front-loaded purpose and the when/when-not clauses are well structured, but the block about "each pitch returned is counted as a view" and opening pitch links adding sparks is boilerplate copied from a pitch-returning tool and is dead weight here. That inapplicable content materially dilutes an otherwise tight definition.

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 zero-parameter health check with an output schema, the description covers availability, version reporting, auth requirements, rate-limit isolation, and logging, so an agent has enough to call it correctly. Completeness is only slightly undercut by the misleading pitch-view and spark-count sentences that do not apply to this endpoint.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The only parameter-adjacent information the description adds is that no API key is needed, which the empty schema cannot express.

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?

"Check that PitchSpark's startup pitch service is answering ... and which API version it speaks" is a specific verb-plus-resource statement with added scope (availability + version). It explicitly separates itself from the data siblings: "Do not use for: finding startups or reading pitches; it returns no pitch data."

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description uses explicit "Use when" and "Do not use for" clauses, so both the positive trigger (a pre-flight availability check) and the exclusion (searching or reading pitch content) are unambiguous. It also names the sibling to use for the excluded case (pitchspark_search_pitches_v1).

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