Skip to main content
Glama
Open Market Research MCP

Open Market Research MCP

by mgifford

normalize_public_metadata

Normalize local code.json, agency-index.json, or publiccode.yml text into consistent metadata for market research and review without making network requests.

Instructions

Normalize local code.json, agency-index.json, or publiccode.yml text.

This performs no network request and does not treat metadata as proof of suitability, reuse rights, or accessibility conformance.

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": {
      "metadata_text": "<metadata_text>",
      "metadata_format": "<metadata_format>"
    },
    "name": "normalize_public_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
repositoryNo
source_urlNo
metadata_textYes
metadata_formatYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burdens, and it spends its budget on disclaimers (no network request, outputs are not proof of suitability/reuse/accessibility conformance) rather than operational behavior. It does not say what "normalize" actually does to the text, whether malformed input is rejected or coerced, or what shape the result takes; the caveats are useful caution but thin disclosure.

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?

Two short sentences, no redundant restatement of the name, and the core action is front-loaded. The second sentence earns some of its space as a correctness caveat, though it leans toward policy phrasing rather than invocation guidance.

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

Completeness3/5

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

For a four-parameter transform with no annotations and no output schema, the definition covers the input side adequately but leaves the result shape and half the parameters undocumented. It is not misleading, but an agent still has to guess how repository and source_url affect the normalization.

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?

Schema description coverage is 0% for four parameters, and the description never mentions them. The three filenames imply the values for metadata_format, but the roles of repository and source_url (both defaulting to empty strings) and the required metadata_text are left entirely unexplained in both schema and prose.

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 names a specific verb (normalize) and enumerates the exact resources accepted (code.json, agency-index.json, publiccode.yml text), so an agent knows precisely what input this tool consumes. It does not differentiate against siblings, but the sibling list contains no other normalization tool, so ambiguity risk is low.

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?

"Normalize local ... text" implies the caller must already hold the metadata locally, and the no-network disclaimer reinforces that this is an offline transform rather than a fetch. It never states explicitly when to choose this over other steps, nor any prerequisite or exclusion beyond the network note.

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