Skip to main content
Glama

get_my_rules

Read-onlyIdempotent

Retrieve all governance rules that apply to you—workflow constraints, assignment policies, and behavioral requirements—merged from workspace and project levels before acting in a project.

Instructions

Get ALL governance rules that apply to you: workflow constraints, assignment policies, behavioral requirements. Includes workspace and project-level rules with source annotations. This is the one to call before acting in a project: get_project_rules lists every rule configured there whoever it targets, get_assignment_rules and get_workflow_rules return a single rule family.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNoOptional project UUID. With it, returns the effective rules for that project (workspace rules merged with the project's own); without it, workspace-level rules only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • changedInput schema / properties / project_id / description
      Previous value: -"Optional project ID to get project-specific effective rules."New value: +"Optional project UUID. With it, returns the effective rules for that project (workspace rules merged with the project's own); without it, workspace-level rules only."
  2. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that the tool is read-only, idempotent, non-destructive, and closed-world, so the description does not need to repeat safety traits. It adds useful behavioral context by stating that the result includes workspace-level and project-level rules with source annotations, though it does not describe rate limits, auth requirements, or response shape.

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 three compact sentences with no wasted clauses. It is front-loaded with the core purpose and then moves efficiently into scope and sibling-tool differentiation.

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

Completeness5/5

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

For a one-parameter, read-only tool with rich annotations and full schema description coverage, the description provides enough context to call it correctly. It explains what rules are returned, the workspace/project-level scope, and when to prefer this tool over sibling rule-listing tools.

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?

The input schema has 100% description coverage for the single project_id parameter, including the distinction between providing a UUID and omitting it. The description does not add parameter-level detail beyond the schema, so the baseline score of 3 is appropriate.

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 a specific verb and resource: "Get ALL governance rules that apply to you," and enumerates the rule categories (workflow constraints, assignment policies, behavioral requirements). It explicitly distinguishes itself from sibling tools get_project_rules, get_assignment_rules, and get_workflow_rules, so an agent can select it without opening other schemas.

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?

It gives a clear triggering condition: "This is the one to call before acting in a project." It also contrasts alternatives by explaining that get_project_rules lists every configured rule regardless of target, while get_assignment_rules and get_workflow_rules return only a single rule family.

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