Skip to main content
Glama

Tool permission matrix

submit_tool_permission_matrix
Idempotent

Map each tool to the scopes that authorise it and flag tools with no scope. When reviewing which tools an agent may call and under what scope. Do not choose this when you need enforcement, which needs the runtime. Example requests: Build a permission matrix for these tools and scopes. | Which tools have no scope? | Map my agent tools to their permissions.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_tool_permission_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior2/5

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

Annotations already declare the safety profile (idempotent, non-destructive, not read-only), and the description adds nothing beyond that. Critically, it never discloses that this is a priced job requiring a quote_id and explicit authorization, nor that the schema's 'accepted_price' is checked against a stored quote and can be refused if the price moved.

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?

Purpose is front-loaded and the total length is short. The 'When reviewing...' sentence is a fragment and the three example requests are somewhat redundant with the opening sentence, but none of it is misleading or padded to the point of obscuring the core statement.

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?

An output schema and annotations are present, so return format and safety need not be restated. However, for a four-parameter tool that submits an asynchronous, priced job with quote validation, omitting any mention of the quote/authorize flow leaves a meaningful hole an agent must discover from the schema alone.

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

Parameters3/5

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

Schema description coverage is a moderate 75%, with the tools/scopes inputs well documented in the schema, so the schema carries most of the weight. The description adds only indirect hints via example requests and says nothing about the authorization parameters (quote_id, authorized_by, accepted_price), which are the ones an agent is most likely to get wrong.

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 opens with a specific verb and resource: 'Map each tool to the scopes that authorise it and flag tools with no scope.' That is concrete enough to separate this capability from the many other submit_* analysis tools, and it states the two outputs (mapping and no-scope flags).

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?

It names the situation to use it in ('When reviewing which tools an agent may call and under what scope') and an explicit exclusion ('Do not choose this when you need enforcement, which needs the runtime'). The gap is that no concrete alternative tool or runtime entry point is named, so the agent must infer where to route enforcement requests.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources