Skip to main content
Glama
Sign In
sop-mcp

sop-mcp

by ValueArchitectsAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_resource

Fetch resource content via URI to obtain specific SOP details required for executing standard operating procedures.

Instructions

Read a resource by its URI.

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": {
      "uri": "<uri>"
    },
    "name": "read_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
uriYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.12.2

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Read', implying a non-destructive operation, but provides no details about error behavior, authentication requirements, or resource existence handling. The description adds minimal value beyond what the name already suggests.

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?

The description is a single sentence with no wasted words, achieving high conciseness. However, it is so brief that it borders on under-specification. For the purpose of being concise, it scores well, though it lacks substance.

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?

Given the simple schema and lack of output schema or annotations, the description is quite incomplete. It does not explain what happens when a resource is not found, whether the URI must be fully qualified, or any other context. This makes the tool minimally viable but with clear gaps.

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?

The schema has 0% description coverage and the parameter is just a required 'uri' string. The description mentions 'by its URI', which is minimally helpful but does not explain what constitutes a valid URI, any formats, or examples. It adds little beyond the schema's parameter name and type.

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 uses a specific verb ('Read') and resource ('resource'), and clarifies the identifier type ('URI'). While it doesn't explicitly differentiate from sibling tools like list_resources, the name and action imply a single-resource read operation, which is reasonably clear.

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?

The description gives no guidance on when to use this tool versus alternatives. It merely states what it does without any context about appropriate use cases, limitations, or exclusions. Sibling tools like list_resources could overlap, but no differentiation or selection criteria are provided.

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

Deploy Server

Other Tools