Skip to main content
Glama

Tools for Agents

by io.github.max124vip-dev
OverviewDiscussionsAdmin

xml_parse

Parse XML and extract tag values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoOptional tag to extract values from
textYesXML text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / args
      Removed value: -{
-  "description": "Tool arguments",
-  "properties": {
-    "text": {
-      "description": "Primary input text",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Optional tag to extract values from",
+  "type": "string"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "XML text",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "text"
+]
  2. Added

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must convey behavioral traits itself. It only states the core function without disclosing error handling, return format, or behavior with malformed XML or multiple matching tags.

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 a single sentence, 'Parse XML and extract tag values,' with no unnecessary words. It is appropriately brief for the tool's apparent simplicity.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks return format, error behavior, and usage context. With no output schema and no annotations, it leaves the agent uncertain about what the tool returns and how to handle edge cases.

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 schema provides descriptions for both parameters, achieving 100% coverage. The description adds that tag values are extracted, which aligns with the params, but does not provide additional syntax or format details.

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 description uses specific verbs 'Parse' and 'extract' with a clear resource 'XML' and target 'tag values'. It distinguishes itself from sibling parse tools like csv_parse or json_parse by focusing on XML and tag extraction.

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 guidance is provided on when to use this tool over alternatives like other parse tools. The description does not mention exclusions, prerequisites, or alternative tools.

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

All Tools for Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources