Skip to main content
Glama

Primer Market Systems (MSD) & DCED Engine

get_opportunity

Read-onlyIdempotent

Retrieve complete structured metadata and official links for a single active MSD or Social Enterprise opportunity by numeric ID.

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": {
      "id": "<id>"
    },
    "name": "get_opportunity"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric opportunity ID returned by search_opportunities.

Output Schema

NameRequiredDescriptionDefault
foundNo
opportunityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds one genuine behavioral fact beyond them — that only 'active' opportunities are returned — but says nothing about what happens for an unknown or inactive ID, which matters for a lookup keyed on an external ID.

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

Conciseness5/5

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

One sentence, front-loaded with the verb and resource, with zero padding. Every clause carries information: scope, supported entity types, key type, and the active-only restriction.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. The description is nearly complete for a one-parameter lookup; the only material gap is not stating the failure mode for non-existent or inactive IDs.

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 is already documented as a numeric opportunity ID returned by search_opportunities. The description's 'by numeric ID' adds no format, range, or validation detail beyond the schema, so the baseline 3 applies.

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 (retrieve), a specific resource (MSD or Social Enterprise opportunity), and an explicit scope (single, active, by numeric ID). The 'single ... by numeric ID' framing lets an agent distinguish it from the sibling search_opportunities list tool without opening either schema.

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 only implied: the schema says the ID comes from search_opportunities, and 'single ... by numeric ID' signals a follow-up detail lookup after a search. There is no explicit when-to-use or when-not-to-use statement, and no stated behavior for IDs that are inactive or not found.

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.