Skip to main content
Glama

QueryMind

Propose an access rule

set_access_rule
Destructive

Propose which rows a role can access. Changes take effect only after an administrator reauthenticates and confirms through a secure link, never through chat alone.

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": {
      "role": "<role>",
      "table": "<table>",
      "predicate": "<predicate>"
    },
    "name": "set_access_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRole affected by the rule.
tableYesTable to which the rule applies.
predicateYesSQL WHERE condition, for example dept_id = 101.
descriptionNoBusiness explanation of the proposed rule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds meaningful context beyond them by explaining that the proposal is inert until an administrator reauthenticates and confirms through a secure link, and that chat confirmation is never sufficient. That deferred-effect and auth-requirement detail materially changes how an agent should present the tool. It stops short of covering idempotency or what happens when a rule is re-proposed for the same role/table.

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?

Two short sentences with zero waste; the core purpose is front-loaded and the critical safety caveat follows immediately. Nothing is repeated from the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation-adjacent tool with no output schema and full schema coverage, the description supplies the essential missing piece: the approval gate. The only gap is that an agent does not learn what the call returns or what an already-pending rule means, which matters slightly given no output schema.

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 100%, with each of role, table, predicate, and description documented in the schema itself, including an example predicate. The description adds no additional meaning about parameter formats, constraints, or interactions, so the baseline 3 applies.

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 description states a specific verb and resource: 'Propose which rows a role can access', which pins down both the action (proposal, not enforcement) and the object (row-level access rules). It is clear on its own, though it does not explicitly differentiate itself from any sibling tool by name.

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?

Usage is implied rather than stated: 'Propose' plus the note that changes only take effect after an administrator confirms tells the agent this is a draft step in an approval workflow. There is no explicit when-to-use/when-not-to-use framing or named alternative for applying or reviewing rules.

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