Skip to main content
Glama
Sign In
Debeka MCP Server

Debeka MCP Server

by schmelli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get Debeka Page Info

debeka_get_page_info
Read-onlyIdempotent

Get the current page URL, title, and form elements to debug issues when the form structure changes.

Instructions

Gets information about the current page structure.

Useful for debugging if the form structure has changed.

Returns: Page URL, title, and list of form elements found.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds value by disclosing exact return contents (URL, title, form elements) and framing the tool as a diagnostic inspection, going beyond the structured annotations.

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?

The description is compact: one purpose sentence, one usage context sentence, and a three-item return list. Every line earns its place and the main action is front-loaded.

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?

For a zero-parameter, read-only inspection tool with a simple output, the description is complete: it states what it does, when it is useful, and what it returns. The annotations handle side-effect and idempotency guarantees, so no critical operational detail is missing.

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?

The tool has zero parameters and the schema's property list is empty with 100% coverage, so there is nothing for the description to add. The baseline of 4 applies because no parameter documentation is needed.

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 clearly states the tool gets current page structure and enumerates specific outputs (URL, title, form elements), which makes its purpose concrete. However, it does not explicitly differentiate itself from sibling tools such as debeka_screenshot, so sibling distinction is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear use context: debugging when the form structure may have changed. It does not state when not to use the tool or mention alternative siblings, so it stops short of full routing guidance.

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