Skip to main content
Glama

get_policy

Retrieve the active execution policy and call-chain state, including recursion limits, permissions, timeouts, and default behaviors, to verify runtime constraints before invoking subagents.

Instructions

現在の実行ポリシー(再帰上限・権限・タイムアウト・未指定時の挙動など)と呼び出し連鎖の状態を返す

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_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the categories of information returned (limits, permissions, timeouts, defaults, chain state), which is useful behavioral context, but it never states that the call is read-only/side-effect free, nor whether the policy is per-session or global.

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?

A single front-loaded sentence with the return payload enumerated in a parenthetical. Nothing is redundant, though the trailing など (etc.) leaves the enumeration open-ended rather than definitive.

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?

With no output schema and no annotations, the description must convey what comes back, and it does so by listing the policy facets and chain state. It is close to complete for a zero-parameter getter, missing only whether the snapshot is scoped to the caller or the whole runtime.

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

Parameters4/5

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

The tool takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description correctly implies no input is required by framing the call as a read of current state.

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?

States a specific verb (返す / returns) and resource (現在の実行ポリシー / current execution policy), and enumerates the returned facets: recursion limit, permissions, timeout, default behavior, plus invocation-chain state. That is far more specific than the sibling getters (get_agent, get_run), though it never explicitly contrasts itself with them.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. Usage is only implied by the word 現在の (current), which suggests calling it to inspect live policy state, but the agent must infer that on its own.

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