Skip to main content
Glama

Get manifest addon

get_manifest_addon
Read-only

Read a manifest add-on an Application published to the organisation's catalogue: its catalogue details and published versions. Pass to_version to compare two published versions instead (from_version defaults to the version before it), optionally narrowed to paths. Read-only.

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": {
      "addon_id": "<addon_id>"
    },
    "name": "get_manifest_addon"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsNoCompare versions: only these manifest paths.
addon_idYesThe manifest add-on's id.
to_versionNoCompare versions: the newer version of the comparison.
from_versionNoCompare versions: the older version; omitted compares with the version before to_version.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds genuinely useful behavior: that supplying to_version changes the entire operation into a comparison rather than a read, how from_version defaults, and that paths optionally narrows the diff. The trailing 'Read-only' restates the annotation rather than adding to it, but the mode-switch semantics are real added context.

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?

Three tight sentences with the primary read purpose front-loaded, followed by the comparison mode and its modifiers. The only near-redundancy is the closing 'Read-only', which repeats the annotation, but nothing is padded or buried.

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

Completeness4/5

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

With four parameters, full schema coverage, and no output schema, the description covers both modes and the parameter interplay an agent needs to call it correctly. It does not say what 'catalogue details' comprise or what happens for an unknown version, but those are minor gaps for a read-only tool with a well-documented schema.

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?

Schema coverage is 100%, so all four parameters are already documented in structured fields, including from_version's default. The description's main addition is framing that to_version/from_version/paths collectively trigger compare mode rather than being independent options, which the schema does not convey; otherwise it largely mirrors the schema wording.

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 gives a specific verb ('Read') and resource ('manifest add-on an Application published to the organisation's catalogue'), and it distinguishes the two operating modes (catalogue details/versions vs. version comparison). It does not differentiate itself from nearby siblings such as get_addon_details or get_addon_configuration, so an agent must infer the boundary, but the purpose itself is unambiguous.

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?

Usage is stated at the mode level: pass to_version to switch from reading catalogue details to comparing two published versions, with from_version defaulting to the predecessor and paths narrowing the diff. There is no explicit guidance about when to pick this over the sibling get_* add-on tools, so alternative selection is left to inference.

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.