Skip to main content
Glama
Sign In
parserbee-mcp

parserbee-mcp

Official
by ParserBee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a Parser Template

get_template
Read-only

Retrieve a single ParserBee Parser Template and all its fields by ID to review or reuse its parsing settings.

Instructions

Get one Parser Template with all of its fields.

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": {
      "template_id": "<template_id>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesID of the Parser Template

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the safety burden is covered. The only added context is that all fields are returned ('with all of its fields'), which is minor and says nothing about failure behavior for unknown IDs.

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?

A single short sentence with no filler and the resource front-loaded. It is appropriately sized, though it is arguably too terse to be fully helpful rather than optimally concise.

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?

No output schema exists, and the description partially compensates by indicating the full record is returned. For a one-parameter read tool this is close to sufficient, missing only error/not-found behavior.

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% with a single documented template_id, so the schema carries the parameter meaning. The description adds nothing beyond restating that one template is fetched; baseline 3 applies.

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?

States a specific verb+resource (Get a Parser Template) and the scope of the fetch (one, with all fields). This implicitly separates it from list_templates, but it never names or explicitly contrasts that sibling, so an agent has to infer the boundary.

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?

The word 'one' implies single-item retrieval by ID versus the bulk list_templates, giving implied usage. However, there is no explicit when-to-use statement, no mention of the required template_id prerequisite, and no named alternative.

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

Deploy Server

Other Tools