Skip to main content
Glama

get_effective_csps

Read-onlyIdempotent

Resolve and inspect the contextual security policies effective for a specified team, user, or agent scope to verify applicable access rules.

Instructions

Inspect the contextual security policies effective for the requested scope.

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

Input Schema

NameRequiredDescriptionDefault
team_idNoTeam UUID for resolving team-scoped policies
user_idNoUser UUID for resolving user-scoped policies
agent_idNoAgent UUID for resolving agent-scoped policies

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.4
    • changedInput schema / properties / agent_id / description
      Previous value: -"UUID do agente para resolver CSPs no escopo agent"New value: +"Agent UUID for resolving agent-scoped policies"
    • changedInput schema / properties / team_id / description
      Previous value: -"UUID do time para resolver CSPs no escopo team"New value: +"Team UUID for resolving team-scoped policies"
    • changedInput schema / properties / user_id / description
      Previous value: -"UUID do usuário para resolver CSPs no escopo user"New value: +"User UUID for resolving user-scoped policies"
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only addition is the word 'effective', which suggests a resolution/merge of scoped policies, but it doesn't explain resolution order, precedence between overlapping scopes, or defaults when no scope is given.

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 no filler or repetition. It is efficient, though the brevity comes at the cost of leaving key selection and scoping semantics unstated.

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

Completeness3/5

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

For a read-only tool with three fully documented optional parameters and no output schema, the description is minimally adequate. It nevertheless leaves open the two things an agent must know: how scope parameters combine, and what shape the returned 'effective' policy set takes.

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 description coverage is 100%, and each parameter is documented as the UUID used to resolve team-, user-, or agent-scoped policies, so the baseline applies. The description adds no meaning beyond that, notably omitting how the three optional scope parameters combine when more than one is passed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'inspect' and the object 'contextual security policies' give a recognizable purpose, and 'effective' hints at resolved/inherited policy rather than raw definitions. However, the description never differentiates itself from the sibling tools get_csp and list_csps, so an agent cannot tell from the text alone which one returns the resolved view.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. The phrase 'for the requested scope' implies the three scope parameters exist, but nothing says when a caller should supply team_id vs user_id vs agent_id, or what happens if none is supplied (all three are optional).

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