Skip to main content
Glama
Datris MCP Server

Datris MCP Server

get_agent_policy

Retrieves each action's agent policy to show if it runs automatically, needs approval, or is denied before consequential changes, so you can tell the user whether it will run now or queue.

Instructions

Read this Datris instance's agent policy: for each action (e.g. tap:delete, pipeline:update:dest-types) whether an agent may do it on its own (auto), must wait for a person to approve it (approve), or is refused (deny). Call this before a delete, schema migration, or other consequential change to know whether it will run immediately or queue for approval, and tell the user accordingly. Returns {enabled, policy:{actions, overrides, limits}, actions:[all policy-able action keys], pendingCount}. When enabled is false, every action is auto.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly does: it declares this is a read, enumerates the three policy outcomes with their meanings, and discloses the critical default that "when enabled is false, every action is auto." It doesn't state whether the policy is cached, scoped per-workspace, or how limit values are interpreted, but the decision-relevant behavior is covered.

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?

Front-loaded with purpose, then the call trigger, then return shape, then the enabled=false edge case — a sensible order with no filler. The trigger sentence is unusually dense (delete / migration / consequential change / run-or-queue / tell the user) but every clause adds information.

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?

No output schema exists and none is needed: the description supplies the return structure ({enabled, policy:{actions, overrides, limits}, actions, pendingCount}) plus the disabled-mode behavior. For a zero-argument read tool, an agent has everything required to call it and interpret the result.

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 there is nothing for the description to disambiguate; baseline is the ceiling here. The description instead spends its budget on return-shape semantics, which is the right trade.

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 ("Read this Datris instance's agent policy") and immediately defines the domain: per-action disposition of auto / approve / deny with concrete action-key examples. That framing distinguishes it from approval-instance tools like get_approval without needing to name them.

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 prescribes when to call it: "Call this before a delete, schema migration, or other consequential change to know whether it will run immediately or queue for approval." It also states the follow-up obligation ("tell the user accordingly"), so the agent knows what to do with the answer, not just how to fetch it.

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

Deploy Server

Other Tools