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

MCP Object-Authz Lab

by WRG-11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

note_create_limited

Create a note with a per-client quota of three notes, enforcing the limit by client identity to prevent quota abuse.

Instructions

Create a note with a per-client quota (max 3 notes). The quota is tracked by client identity.

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>",
      "title": "<title>"
    },
    "name": "note_create_limited"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
titleYes
tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.10.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It usefully discloses the quota limit (max 3) and that tracking is per client identity. However, it does not explain what happens when the quota is exceeded, authorization requirements, or the creation outcome, leaving meaningful behavioral gaps.

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?

The description is compact, front-loaded, and each sentence earns its place: the first defines the action and limits, the second clarifies how the limit is tracked. There is no redundant or filler content.

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?

Despite a small parameter set, the lack of annotations, zero schema descriptions, no output schema, and close sibling tools make the description insufficient. An agent cannot confidently determine what 'token' means, how to identify the client, or what error/response to expect when the quota is reached.

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 needed to compensate for the three parameters. It does not mention token, title, or body by name, and 'client identity' is only an oblique reference to what is likely the token. The description adds little beyond the generic act of creating a note.

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 states a specific action and resource: 'Create a note'. It also distinguishes this tool from sibling note_create by naming the per-client quota constraint (max 3 notes), making the tool's specialized role clear.

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?

The quota and client-identity tracking imply this tool is for creating notes under a client-scoped limit, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. The usage context is only implied, not stated.

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