Skip to main content
Glama

vCard FN field count, body discarded

by io.github.sadri-dridi
OverviewDiscussionsAdmin

vcf-ok

vCard FN field count, body discarded

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoGit ref name; discarded after the shape check
urlNoHTTPS URL to normalize or cite
cityNoCity name for a public weather hint; discarded after the call
feedNoPublic RSS or Atom URL; titles discarded
hostNoPublic hostname
jsonNoJSON text to validate; discarded after the check
pathNoFile path to check; no disk access
zoneNoIANA timezone name
queryNoSearch text; discarded after the length check
websiteNoPublic https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / website
      Added value: +{
+  "description": "Public https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.",
+  "type": "string"
+}
  2. First observed

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations at all, the description carries the full burden. 'Body discarded' is the only behavioral hint, but it is not clear what 'body' refers to or whether the tool reads from a file, URL, or stdin. No side effects, auth needs, or rate limits are disclosed.

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

Conciseness2/5

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

Six words and a comma are extremely terse, but this is under-specification rather than conciseness. There is no front-loaded verb and no structure that helps an agent parse the tool's purpose.

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

Completeness1/5

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

For a tool with 10 optional parameters, 30 siblings, no annotations, and no output schema, the description is far too thin. It omits which parameter is needed, what the returned count means, and how the tool relates to its sibling validators.

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

Parameters2/5

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

Although schema coverage is 100%, the parameter descriptions are generic (url, city, host, path, etc.) and none references vCard or FN fields. The tool description adds no semantic bridge between its stated purpose and the available inputs, so an agent cannot determine which parameter carries the vCard data. Baseline of 3 for coverage is undercut by the complete mismatch.

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

Purpose2/5

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

The description is a fragment ('vCard FN field count, body discarded') that identifies a resource (vCard) and an output (FN field count) but lacks a verb and does not explain how the input is provided. None of the 10 parameters mention a vCard, so an agent cannot tell what to pass. It does not differentiate from any sibling, though no sibling is about vCards.

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

Usage Guidelines1/5

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

No information about when to use this tool instead of domain-shape, validate-json, or any other sibling. There is no mention of the conditions that make vcf-ok the right choice, and the meaning of 'vCard FN field count' is left unexplained.

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

All vCard FN field count, body discarded 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