Skip to main content
Glama

get_project_rules

Read-onlyIdempotent

Retrieve every rule configured for a project across workspace and project scope, giving an audit view of the entire rule set and its targets.

Instructions

Get every rule configured for a project (workspace + project scope), whoever it targets: an audit view of the whole rule set. For the rules that bind YOU use get_my_rules; for one family, get_assignment_rules (who gets new work) or get_workflow_rules (allowed status transitions).

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": {
      "project_id": "<project_id>"
    },
    "name": "get_project_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject UUID, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID."New value: +"Project UUID, from list_projects."
  2. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety needs no restating. The description adds real context beyond them by clarifying this is an unfiltered audit view spanning both workspace and project scope, which explains why the result set may be large. It stops short of describing return shape or ordering, keeping it just under 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.

Conciseness5/5

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

Two sentences, zero padding. The scope-defining clause comes first and the disambiguation guidance follows, which is the right order for an agent deciding whether to call this or a sibling.

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?

A single-parameter read tool with full annotation coverage and a fully documented schema needs little more. The description supplies the scope semantics and sibling routing that structured fields cannot express; only output shape is unaddressed, and there is no output schema to lean on, which is a minor gap for an audit-style listing.

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 coverage is 100% and the project_id description already names its source ('from list_projects'). The tool description adds no further meaning about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('Get every rule configured for a project'), plus the exact scope ('workspace + project scope, whoever it targets'). The phrase 'an audit view of the whole rule set' makes the exhaustive nature unmistakable and distinguishes it from the filtered siblings named immediately after.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use get_my_rules for rules binding the caller, get_assignment_rules for who gets new work, get_workflow_rules for allowed status transitions. Each alternative comes with the condition that selects it, leaving nothing to inference.

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