Skip to main content
Glama
Sign In
cmcp

cmcp

by DeveshB-1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

[draft] Auth: OAuth2.0/OAuth2.0 Get Resource

draft_auth_oauth2_0_oauth2_0_get_resource
Read-only

Fetch an authenticated user's resource using an OAuth2 bearer token in the Authorization header; requests without this header return 401 Unauthorized.

Instructions

Once the bearer token has been obtained, it can be passed as Authorization header to access user's resources.

Authorization: Bearer vp7jx...

If the Authorization header is not passed the endpoint returns 401 Unauthorized.

(Postman request: [draft] Auth: OAuth2.0/OAuth2.0 Get Resource | GET https://postman-echo.com/oauth2/user/info)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "draft_auth_oauth2_0_oauth2_0_get_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior: the Authorization header is required and a missing header yields 401 Unauthorized. It stops short of describing the response payload, which matters because there is no output schema.

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

Conciseness3/5

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

Front-loading is poor: the opening sentence is about token mechanics, not about what the tool does, and the raw Postman request line with a full URL is filler for an agent that already has the tool identity. The 401 warning is the one sentence that truly earns its place.

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?

With zero parameters and no output schema, the description carries the burden of describing the return value, and it does not — the agent cannot tell what the user info payload contains. Auth requirements and error behavior are covered adequately, making it minimally viable but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description adds value by documenting the one implicit input the schema does not capture — the Authorization: Bearer header — including its format example and failure mode.

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

Purpose2/5

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

The description never states the operation beyond the title's 'Get Resource'; it explains how to authenticate rather than what data is retrieved. A caller learns the endpoint is GET /oauth2/user/info only from the trailing Postman request line, and nothing distinguishes this from the sibling draft_auth_oauth2_0_oauth2_0_get_access_token.

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?

It establishes a clear prerequisite — a bearer token must already have been obtained — which implies sequencing after the get_access_token sibling. However, it never names that sibling explicitly or says when not to use this tool, leaving the routing inference to the agent.

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