Skip to main content
Glama
Sign In
MCP Object-Authz Lab

MCP Object-Authz Lab

by WRG-11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

note_share_redeem

Redeem an opaque share grant to access a shared note, enabling validation of object-level authorization in multi-tenant workflows.

Instructions

Redeem an opaque share grant produced by note_share_prepare.

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": {
      "token": "<token>",
      "grant": "<grant>"
    },
    "name": "note_share_redeem"
  }
}

Input Schema

NameRequiredDescriptionDefault
grantYes
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.10.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It mentions that the grant is opaque and tied to note_share_prepare, but it does not say whether redemption consumes the grant, mutates access, requires specific auth, or what the response contains.

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 tightly written sentence with no filler. The verb and object come first, and every word contributes meaning, including the critical linkage to note_share_prepare.

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?

With no annotations and no output schema, the description leaves important operational context unexplained: what a successful redemption returns, whether the grant is single-use, and what error cases may arise. The link to note_share_prepare helps but does not cover these 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?

Schema description coverage is 0%, so the description must compensate. It only echoes the concept of a 'share grant' without clarifying the distinct roles of 'token' and 'grant', their format, or how the two relate.

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?

The description uses the specific verb 'redeem' with a clear resource, 'an opaque share grant produced by note_share_prepare.' This identifies both the action and the exact provenance of the input, distinguishing it from every sibling tool by naming its paired producer.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'produced by note_share_prepare' gives clear contextual guidance: use this tool when you have a grant from that preparation step. It does not explicitly enumerate exclusions or alternative tools, so it stops short of full 5-level guidance.

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