Skip to main content
Glama
Sign In
dashclaw

dashclaw

by ucsandman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

dashclaw_policies_list

List active governance policies to see which rules apply before taking actions. Filter by agent to calibrate risk scores and identify action types requiring approval.

Instructions

List active governance policies. Use this to understand what rules govern your actions before taking them. Helps calibrate risk scores and know which action types require approval. Optionally filter to policies applying to a specific agent.

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": "dashclaw_policies_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idNoFilter to policies applying to a specific agent

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It states 'active governance policies', implying read-only and non-destructive behavior. However, it does not disclose additional traits like rate limits, return format, or whether inactive policies are excluded. Adequate but minimal.

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?

Three sentences, no wasted words. Front-loaded with the core action, then usage context, then optional filter. Every sentence earns its place.

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 simple tool with one optional parameter and no output schema, the description covers purpose, when to use, and the filter option. It is complete for the agent to understand and invoke correctly.

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 parameter agent_id has a clear description. The description adds no extra meaning beyond what the schema already provides, so baseline 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?

Description clearly states 'List active governance policies' with a specific verb and resource. It also explains the purpose of understanding rules before actions, which distinguishes it from sibling tools like check_policy (checks a specific policy) and list_policy_rules (lists rules).

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

Usage Guidelines4/5

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

Explicitly tells agents when to use: 'before taking actions' and to understand governing rules. Mentions optional filtering by agent. Does not explicitly state when not to use, but the guidance is clear and actionable.

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