Skip to main content
Glama

LivedProof (demo)

Get verified-user answers

get_verified_answers
Read-only

Answers from people with checked proof that they pay for the tool, with proof level, date and sample size. NOT LIVE YET: always returns status coming_soon and count 0 until the service launches.

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": {
      "tool": "<tool>"
    },
    "name": "get_verified_answers"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
questionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new behavioral context: the tool is a stub that returns a coming_soon status with zero count until launch. It also discloses the shape of returned metadata (proof level, date, sample size) despite no output schema, which is exactly the kind of value beyond annotations being scored here.

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?

Two sentences, no filler, with the availability warning front-loaded in caps so an agent cannot miss it. The first sentence is dense but every clause (proof level, date, sample size) conveys return-value information.

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 two-parameter read tool with no output schema, the description adequately explains the return semantics and the non-functional launch state, but it leaves the parameters entirely unexplained and does not say what happens if 'question' is omitted.

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

Parameters2/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 carry the burden for the two parameters, yet it never explains what 'tool' identifies or whether 'question' is a required filter or free-text query. The reference to 'the tool' is at best an oblique hint, leaving the required parameter's meaning undefined.

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 resource and its distinguishing attribute: answers only from users with checked proof of payment, including proof level, date, and sample size. An agent can tell this apart from generic lookup tools, though it never explicitly contrasts with siblings like lookup_tool or proof_levels.

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?

There is a strong implicit usage caveat — 'NOT LIVE YET: always returns status coming_soon and count 0' tells the agent not to rely on results — but no positive when-to-use guidance and no named alternative for getting answers in the meantime.

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