XML.now MCP Server

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

Annotations already declare openWorld=true and destructive=false, yet the description adds real value by disclosing SSRF protections: private-network URLs and embedded credentials are rejected before the request is made. It still doesn't say what happens when wait_for_completion is false or how failures surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences: the action and pipeline come first, the rejection constraints second. Nothing is padded and no sentence is wasted.

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

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

An output schema exists, so return values needn't be spelled out, and the security constraints are well covered. But for a 9-parameter tool with zero schema descriptions, the undocumented image/resize parameters leave an agent unable to use most of the surface confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage across 9 parameters, the description is the only source of meaning, yet it covers only source_url and converter, and gestures at wait_for_completion. The image-oriented parameters (width, height, quality, background_color, strip_metadata) go entirely unexplained and are actively confusing for a tool described as converting XML files.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb chain (download, submit, optionally wait) and names the target service (XML.now) plus the converter-slug requirement. However, it must carry the load of resolving the mismatch between the tool name 'convert_image_url' and its stated purpose of converting XML/data files, which it does only implicitly.

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

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

It clarifies that waiting is optional, which implies the async path, but it never names get_conversion_status as the polling alternative or list_converters as the way to obtain a valid slug. Usage is inferable but not routed.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that results are scoped to the caller (no user or workspace target), which is useful, but says nothing about refresh cadence, rate-limit windows, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with zero waste, front-loaded with the verb and the three returned quantities.

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

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

With an output schema present, the return shape needs no explanation, and annotations cover safety and the open-world nature. A brief note on when quota data is refreshed would make it fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies. The word 'caller's' usefully signals the implicit subject of the query is the authenticated identity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Return') and enumerates the exact resources returned: API credits, usage, and rate limit. It is clearly distinct from the conversion-oriented siblings, though it does not explicitly name them.

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

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

Usage is only implied — an agent can infer this is for checking quota/credit status, but the description states no when-to-use context or preconditions. With no alternative tools competing for this purpose, the gap is minor but present.

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

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

Beyond the 'readOnlyHint' annotation, the description provides critical behavioral context regarding the return data: a successful job is indicated by the presence of an 'absolute, temporary download URL.' This is vital operational knowledge for the agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is highly concise, consisting of two efficient sentences that front-loads the resource type and the key benefit of the operation.

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

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

For a read-only status check, the definition is highly complete. It identifies the resource, the action, and explicitly defines what the successful output will contain, giving the agent all necessary context to use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description lacks semantic detail regarding the 'job_id' itself (e.g., format or expected structure). Since the schema is extremely thin, the description cannot significantly compensate, resulting in a baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it checks the status of an 'XML.now conversion job.' This is a precise verb+resource combination that effectively differentiates it from list-based sibling tools.

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

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

The description implies usage by detailing the outcome of a 'completed job' (a temporary download URL). However, it does not provide explicit guidance on when to use this status check versus, for example, initiating a conversion using a different tool.

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, and the description adds that results are slugs rather than full converter objects. It does not mention whether the catalog is cached, how many results come back, or how matching works. No contradiction with openWorldHint despite the word 'live'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler, and the slug examples earn their place by showing the exact output format an agent should expect.

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

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

An output schema exists, so return values need not be explained, but the description does nothing to cover its two undocumented parameters and offers no routing guidance against the three siblings. Adequate to call the tool, not adequate to call it well.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both parameters (limit, search) are undocumented anywhere except their titles and defaults. The description's use of the verb 'Search' faintly gestures at the search param but gives no guidance on matching semantics, while the limit parameter and its 1-100 cap are never mentioned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the live XML.now converter catalog') and clarifies the return type with concrete slug examples (xml-to-json, xml-to-csv). It is distinguishable from siblings by resource, though it never explicitly contrasts itself with convert_image_url or get_conversion_status.

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

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

Usage is only implied: returning 'valid converter slugs' hints that this is a discovery step before calling a conversion tool, but the description never states when to use it, when not to, or which sibling to prefer. No prerequisites or exclusions are given.

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