Skip to main content
Glama

Get software details

get_software
Read-onlyIdempotent

Get one software record with its evidence and the requests it has been proposed for. USE WHEN you need details, sources or verification status for a software_id (or slug) from search results. NO side effects; public. Text fields come in the record's own language; translations holds the other language (English/Chinese) when the submitter provided it, so answer from the version in the user's language. Report unknown fields as unknown; 'unreviewed' records and 'claimed' evidence are not independently verified. Recovery: NOT_FOUND means the ID is wrong; search again.

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": {
      "software_id": "<software_id>"
    },
    "name": "get_software"
  }
}

Input Schema

NameRequiredDescriptionDefault
software_idYesSoftware ID (sw_...) or slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real context beyond them: text fields are in the record's `language`, `translations` holds the counterpart language, and 'unreviewed' records / 'claimed' evidence are not independently verified — an important epistemic caveat for interpreting results.

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?

Front-loaded with purpose, then trigger, then behavioral caveats, then error recovery — a sensible ordering with no filler sentences. It is dense and slightly cramped into one block, but each clause (language handling, verification status, NOT_FOUND) carries distinct information.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does it: it names the payload (record, evidence, proposals), explains language/translation behavior, flags unverified data, and describes the error case. For a one-parameter read tool this is complete enough to call and interpret correctly.

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% and the single parameter already documents 'Software ID (sw_...) or slug', so the description adds little about the input itself beyond repeating '(or slug)'. Baseline 3 applies because the schema does the documentation work here.

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

Purpose5/5

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

States a specific verb and resource — 'Get one software record' — and enumerates what comes with it (evidence and the requests it has been proposed for). The phrase 'from search results' implicitly separates it from search_software, which returns many hits, so an agent can tell the single-record fetch apart from a listing.

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

Usage Guidelines5/5

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

Gives an explicit trigger: 'USE WHEN you need details, sources or verification status for a software_id (or slug) from search results.' It also supplies a recovery path ('NOT_FOUND means the ID is wrong; search again'), which routes the agent back to the search sibling after failure, covering the main decision point for this tool.

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.

Resources