Skip to main content
Glama

Get a verified data board

toolfound_get_verified_board
Read-onlyIdempotent

Boards of listings ranked by data Toolfound fetched itself within the last 7 days: revenue band via Stripe, GitHub stars, or App Store rating. A board is visible only once at least 10 listings have data of that kind; otherwise it returns visible false and no entries.

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": {
      "board": "<board>"
    },
    "name": "toolfound_get_verified_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesWhich kind of Toolfound-fetched data to rank by: Stripe revenue band, GitHub stars, or App Store rating. Check the visible flag in the response, since a board stays hidden until enough listings have data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / board / description
      Previous value: -"Which board: revenue, stars or rated."New value: +"Which kind of Toolfound-fetched data to rank by: Stripe revenue band, GitHub stars, or App Store rating. Check the visible flag in the response, since a board stays hidden until enough listings have data."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond them: a 7-day freshness window and a 10-listing gate that yields visible false with no entries.

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?

Two sentences, both front-loaded with the high-value facts: what is ranked first, the freshness constraint second, the visibility gate last. No filler and no repetition beyond what is needed to be self-contained.

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?

With no output schema, the description carries the return-behavior burden and does so by explaining the visible false / no entries outcome. For a one-parameter read tool with full annotation coverage, this is close to complete, though it says nothing about ordering ties or how many entries a visible board holds.

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 100% and the single enum parameter is already fully documented, including the advice to check the visible flag. The description restates the same three board kinds and the same visibility condition rather than adding format, ordering, or error-detail beyond the 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?

The description uses a specific verb and resource — boards of listings ranked by data Toolfound fetched itself — and pins down the three ranking sources (Stripe revenue band, GitHub stars, App Store rating). It implicitly separates this tool from self-reported signals, but never names a sibling tool the agent should prefer instead.

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

Usage Guidelines3/5

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

Usage is implied by the description of what a board is and the 10-listing threshold, so an agent can infer the intended case. There is no explicit when-to-use versus when-to-use-something-else guidance, and no alternative is named for the case where a board is unavailable.

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