Skip to main content
Glama

Get security report

get_security_report
Read-onlyIdempotent

Return a trusted package security report visible to this connection.

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": {
      "security_report_id": "<security_report_id>"
    },
    "name": "get_security_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
security_report_idYes

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 closed-world, so the safety profile is covered. The description adds a genuinely useful access-control fact ("visible to this connection"), which tells the agent results are connection-scoped. It says nothing about behavior when the ID is unknown or inaccessible, which for a read of a permissioned resource would have been worth one clause.

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 filler, appropriately sized for a narrow getter. Its brevity is close to the limit of usefulness, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the annotation set covers safety semantics. The remaining gap is the missing link between the required security_report_id and how an agent obtains one, which matters for a permissioned lookup tool.

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%: the single parameter is documented only as a UUID pattern with no prose, and the description never mentions the report ID at all. With one required parameter, the description should say what the ID identifies and where it comes from; it does neither.

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?

States a specific verb and resource ("Return a trusted package security report") and scopes it to what is visible to this connection, which distinguishes it from the skill/collection listing siblings. It stops short of naming a sibling or alternative retrieval path, so it is clear but not fully differentiated.

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 guidance on when to call this tool versus alternatives, no stated prerequisites, and no exclusion cases. The agent must infer that it is the lookup path for a report referenced elsewhere.

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