Skip to main content
Glama

Software application metadata

bpj_software_app_metadata
Read-onlyIdempotent

Build SoftwareApplication metadata from supported operating systems, version and download URL.

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": {
      "name": "<name>",
      "systems": "<systems>",
      "version": "<version>",
      "url": "<url>"
    },
    "name": "bpj_software_app_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameYes
systemsYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, and openWorld=false, so the safety profile is fully covered by structured data. The description adds essentially nothing beyond that: it does not say the output is a JSON-LD/metadata string, whether inputs are validated, or how the 'systems' list is serialized.

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?

A single front-loaded sentence with no redundant phrasing. It is efficient, though the brevity borders on under-specification rather than disciplined conciseness.

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?

With four required parameters, no output schema, and zero schema description coverage, the definition leaves key information unstated: what the tool returns, how the inputs are combined, and what the url field actually accepts. For a constructor tool with no output schema, the description should at least characterize the produced artifact.

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%, so the description must compensate, but it only names three of the four parameters and omits 'name' entirely. Worse, it calls the url input a 'download URL' while the schema titles it 'Page URL', leaving ambiguity about what that field should contain; the multi-line format for 'systems' is conveyed only by the schema title.

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 ('Build') and a specific resource ('SoftwareApplication metadata'), plus the inputs it is assembled from, so the agent knows this constructs schema.org-style markup rather than fetching anything. It does not explicitly contrast itself with the sibling *_metadata builders, but the resource name is distinctive enough to separate it from the ISBN, recipe, or product tools.

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?

There is no when-to-use guidance, no statement of the triggering scenario (e.g., emitting structured data for a software product page), and no exclusions or alternatives. The agent must infer appropriate invocation purely from the resource name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.