Skip to main content
Glama

founder_panel_tally

Aggregate yes/no/undecided tagged panel answers to summarize buyer feedback; treat results as unverified signals, not proof of market demand.

Instructions

Aggregate supplied synthetic/actual tagged panel answers (yes/no/undecided); results are not evidence of market demand unless independently verified.

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": {
      "answers": "<answers>"
    },
    "name": "founder_panel_tally"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden, and it does disclose one genuinely useful trait: the output is not evidence of market demand unless independently verified. However, it never says whether the tool is a pure read-only computation, whether results are persisted, whether it requires prior initialization, or how large inputs are handled (the schema allows up to 10,000 items).

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?

One sentence, with the primary action front-loaded before the semicolon-joined caveat. Every clause carries information: what it does, what the input domain is, and the interpretive limit on the output.

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

Completeness3/5

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

For a single-parameter tool with no output schema and no annotations, the description covers the input side adequately but leaves the return shape entirely unspecified — an agent cannot tell whether it gets raw counts, percentages, or a per-respondent breakdown, which is the core output of a 'tally' tool.

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 description coverage is 0%, so the description must compensate, and it partially does: 'tagged panel answers (yes/no/undecided)' explains the array's purpose and maps to the buy enum. It says nothing about the required id field, the optional free-text reason, or the 1–10,000 item bounds, so half the parameter semantics remain undocumented.

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?

The description names a specific verb and resource: 'Aggregate supplied ... tagged panel answers' with the answer domain '(yes/no/undecided)'. The word 'supplied' makes clear it consumes answers rather than generating them, which distinguishes it from a sibling like founder_panel_initialize. It falls short of a 5 only because it never names or contrasts an alternative tool.

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?

'Supplied' implies the answers must come from elsewhere (presumably founder_panel_initialize), but that dependency is never stated and no alternative is named. There is no when-to-use or when-not-to-use guidance; the closing caveat is an epistemic disclaimer, not routing advice.

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