Skip to main content
Glama

Auth: Others/OAuth1.0 Verify Signature

auth_others_oauth1_0_verify_signature
Read-only

Verify OAuth 1.0a request signatures to confirm client-side signing works; returns debug values when verification fails.

Instructions

OAuth1.0a is a specification that defines a protocol that can be used by one service to access "protected" resources (endpoints) on another service. A major part of OAuth1.0 is HTTP Request Signing. This endpoint allows you to check whether the request calculation works properly in the client.

The endpoint supports the HTTP Authorization header. In case the signature verification fails, the endpoint provides the four debug values,

  • base_uri

  • normalized_param_string

  • base_string

  • signing_key

For more details about these parameters, check the OAuth1.0a Specification

In order to use this endpoint, you can set the following values:

Consumer Key: RKCGzna7bv9YD57c

Consumer Secret: D+EdQ-gs$-%@2Nu7

If you are using Postman, also check the "Add params to header" and "Auto add parameters" boxes.

(Postman request: Auth: Others/OAuth1.0 Verify Signature | GET https://postman-echo.com/oauth1)

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": "auth_others_oauth1_0_verify_signature"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the endpoint supports the Authorization header, returns four named debug fields (base_uri, normalized_param_string, base_string, signing_key) on verification failure, and is a Postman Echo GET at postman-echo.com/oauth1. It does not describe the success response shape, which keeps it from a 5.

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

Conciseness2/5

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

Roughly 250 words for a no-parameter echo endpoint, opening with a generic OAuth protocol definition before reaching the tool's actual purpose. The debug-field list, spec link, sample credentials, and Postman checkbox advice are all useful but could be compressed to a few lines; the structure buries the call-relevant information.

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?

The description covers how to invoke it (credentials, Authorization header, URL) and what happens on failure, but with no output schema it leaves the success response undefined. For a verification endpoint, an agent cannot tell what a passing result looks like from the definition alone.

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?

Zero parameters, so the schema is trivially complete and the baseline of 4 applies. The description still adds value by explaining that the signature is carried in the HTTP Authorization header rather than as a query or body parameter, which the empty schema cannot convey.

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 third sentence states a specific verb and resource: 'check whether the request calculation works properly in the client' for OAuth1.0 HTTP Request Signing, which is distinguishable from the digest, basic-auth, and OAuth2 siblings. However, the first two sentences describe the OAuth1.0a spec in general rather than this tool, so the purpose is not front-loaded.

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?

'In order to use this endpoint, you can set the following values' gives concrete credentials and Postman settings, implying a client-debugging use case. It never states when to choose this over auth_digest_digestauth_request or the OAuth2 siblings, nor any exclusions, so usage is implied rather than explicit.

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