Skip to main content
Glama

LivedProof (demo)

Look up a launch tool

lookup_tool
Read-only

Public, sourced facts about a software/AI tool on LivedProof's launch list (vendor, category, link to the official pricing page) plus the status of verified-user answers (coming soon: 0 today). Never returns guesses.

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

Input Schema

NameRequiredDescriptionDefault
toolYesTool name, e.g. 'Cursor' or 'Canva Pro'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 and openWorldHint=false, so the safety profile is covered. The description adds two genuinely behavioral facts beyond that: results are sourced/public and 'never guesses', and the verified-answer count is currently 0 — but it is silent on what happens when the tool name is not on the list (error vs. empty result).

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 front-loaded sentence with no filler; the returned fields, the sourcing guarantee, and the empty-answers caveat are all packed into it without redundant restatement of the tool name.

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 one-parameter read-only lookup with no output schema, the description is largely self-sufficient: it lists the returned fields and warns that answer data is not yet available. The only material gap is the not-found / unknown-tool outcome, which an agent would otherwise have to discover empirically.

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?

The single parameter has 100% schema coverage including concrete examples ('Cursor', 'Canva Pro'), so the schema already does the heavy lifting. The description only adds the constraint that the name must refer to something on LivedProof's launch list, which is a small but real semantic addition.

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 (facts about a tool on LivedProof's launch list) and enumerates the fields returned (vendor, category, official pricing link, verified-answer status), so the agent knows exactly what it fetches. It does not name the sibling tools it is distinct from, so sibling differentiation is only implicit via 'launch list'.

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: look up one named tool on the launch list. There is no explicit when-to-use vs. when-not guidance, and neither list_launch_tools nor get_verified_answers is named as the alternative for browsing or for actual answers — the 'coming soon: 0 today' note hints at the latter but leaves the routing to inference.

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