Skip to main content
Glama

list_csps

Read-onlyIdempotent

Lists contextual security policies in the current tenant and filters them by scope, active status, policy type, or target ID for policy review and management.

Instructions

List contextual security policies in the current tenant.

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

Input Schema

NameRequiredDescriptionDefault
scopeNoFilter by policy scope
is_activeNoFilter by active or inactive status
policy_typeNoFilter by policy type
scope_target_idNoFilter by target ID: agent_id, team_id or user_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.4
    • changedInput schema / properties / is_active / description
      Previous value: -"Filtrar por status ativo/inativo"New value: +"Filter by active or inactive status"
    • changedInput schema / properties / policy_type / description
      Previous value: -"Filtrar por tipo de política"New value: +"Filter by policy type"
    • changedInput schema / properties / scope / description
      Previous value: -"Filtrar por escopo da política"New value: +"Filter by policy scope"
    • changedInput schema / properties / scope_target_id / description
      Previous value: -"Filtrar por ID do alvo (agent_id, team_id, user_id)"New value: +"Filter by target ID: agent_id, team_id or user_id"
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description contributes only the tenant scoping; it says nothing about pagination, result ordering, or whether filters combine with AND semantics.

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 zero filler or redundancy. Its brevity borders on under-specification, but nothing in it is wasted.

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 four-filter list tool with no output schema, the definition covers the core intent but leaves return shape, pagination, and filter-combination behavior unstated. Adequate to invoke, not complete enough to predict results.

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% with four optional, well-documented filters including two enums, so the schema carries the parameter burden. The description adds no filter semantics beyond the schema, making the baseline 3 the correct score.

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?

Description gives a clear verb+resource ("List contextual security policies") and expands the CSP acronym while scoping it to "the current tenant." It does not distinguish this from sibling get_effective_csps, so an agent cannot tell from the description alone which one it needs.

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 and no exclusions. The sibling get_effective_csps exists but is never mentioned, so the agent must infer whether to list raw policies here or fetch effective policies there.

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