Skip to main content
Glama
Billdr MCP Server

Billdr MCP Server

billdr_read

Read the current Billdr page to extract text and numbered buttons, links, and fields, optionally limited to a specific element.

Instructions

Read the current Billdr page: its text and numbered buttons, links and fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "billdr_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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 carries the full burden; it does usefully disclose the return payload (text, numbered buttons, links, fields), which matters because there is no output schema. It never states that the operation is non-mutating, has no side effects on page state, or what happens if no page is loaded. Adequate but incomplete for an annotation-free tool.

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, front-loaded with the action and target, then the payload. Zero filler and nothing that would be better placed later.

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 simple read tool with one optional param, the payload listing compensates for the missing output schema. Gaps remain: no note that reading is side-effect free, no precondition that a page must be open, and no routing to billdr_click/billdr_type which presumably act on the numbered buttons this tool returns.

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 coverage is 100% and the single optional 'element' parameter is documented in the schema as scoping the read to a subtree. The description never mentions the parameter, but the schema does the work, so baseline 3 applies. No added meaning 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?

Specific verb ('read') plus a specific resource ('the current Billdr page'), followed by an enumeration of what comes back: text, numbered buttons, links, fields. That is far more informative than the bare name. It stops short of distinguishing itself from siblings such as billdr_status or billdr_guide, so an agent must infer which of the page-inspection tools is the right one.

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?

No explicit when-to-use statement, no prerequisites (e.g. that a page must already be open via billdr_open), and no mention of alternatives or when not to use it. Usage is only implied by 'current Billdr page'. The agent is left to guess the read-before-act workflow on its own.

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