Skip to main content
Glama

Score a demo

score_demo
Read-onlyIdempotent

A 0–100 quality score for a demo with a short list of fixes, worst first: length and pacing, copy, a clear call to action, personalization, narration, branching, how it works on phones, lead capture, and broken or stale screens. Each fix says what to do and links to where in the editor. Free; with ai: true the AI also reads the copy and rates its clarity (1 AI credit, editors only).

Requires: demos:read.

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": {
      "demoId": "<demoId>"
    },
    "name": "score_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
aiNoAlso have the AI read the copy (1 credit).
demoIdYesDemo id (from list_demos).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantial context beyond them: result ordering (worst first), what each fix contains (an action plus a deep link into the editor), that the base call is free while the AI path costs a credit and is restricted to editors, and the required permission scope. That covers cost, authorization, and response structure – none of which the annotations express.

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?

Purpose and ordering are front-loaded in the first sentence, and the second sentence cleanly separates the paid AI option and the permission requirement. The nine-item dimension list is long but functional – it tells the agent what will be evaluated – though the run-on enumeration costs some scannability.

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

Completeness5/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 full burden of describing the return value and does so: a numeric score, a ranked fix list, and per-fix contents including editor links. Permission scope, cost model, and the AI variant's restriction round out what an agent needs to call this correctly.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an increment: it explains what `ai: true` actually adds (the AI reads the copy and rates its clarity) plus its cost and role restriction, which goes beyond the schema's terse 'Also have the AI read the copy (1 credit).' The `demoId` parameter is not elaborated further, but the schema already anchors it to list_demos.

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?

The first clause names the verb, the resource, and the return shape: a '0–100 quality score for a demo with a short list of fixes, worst first.' It then enumerates the exact dimensions checked (pacing, copy, CTA, personalization, phone behavior, lead capture, stale screens), which lets an agent tell it apart from siblings like get_demo or get_demo_progress without opening a schema.

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?

It states prerequisites ('Requires: demos:read') and a cost/role tradeoff for the paid path ('1 AI credit, editors only'), which is real decision input. But it never says when to prefer this over alternatives such as get_demo or get_analytics, and gives no explicit when-not-to-use condition; usage is only implied by the tool's purpose.

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.