Skip to main content
Glama

get_csp

Read-onlyIdempotent

Retrieve a contextual security policy and its configured rules using a CSP policy UUID to inspect policy settings in Zihin.ai.

Instructions

Retrieve one contextual security policy and its configured rules.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "csp_id": "<csp_id>"
    },
    "name": "get_csp"
  }
}

Input Schema

NameRequiredDescriptionDefault
csp_idYesCSP policy UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / csp_id / description
      Previous value: -"UUID da CSP"New value: +"CSP policy UUID"
  2. First observedv0.1.0

TDQS

A3.6/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 adds one piece of real context beyond that: the response includes the policy's configured rules, not just policy metadata. It says nothing about behavior when the ID is unknown or about the shape/size of the returned rules.

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?

One short sentence, front-loaded with the verb and resource and with the return scope appended. There is no filler, hedging, or restatement of the tool name.

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?

For a simple single-record read with 100% schema coverage, one required parameter, and full annotations, this is nearly complete; mentioning that rules are bundled in the result is the useful part. Minor gaps remain around not-found behavior, but with no output schema there is little else the description is obliged to carry.

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 a single required 'csp_id' UUID parameter, so the schema finishes the job on its own. The description adds no format, lookup, or error semantics for that identifier beyond what the schema states, so the baseline 3 applies.

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?

The description gives a specific verb+resource ('Retrieve one contextual security policy') and scopes it to a single policy, which distinguishes it from the plural/list variants among its siblings. It stops short of naming any sibling explicitly, so differentiation is inferable rather than stated.

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?

Use is only implied: the word 'one' signals single-record lookup by ID, useful to an agent choosing between this and a broader listing call. No when-to-use, when-not-to-use, or named alternative (e.g. get_effective_csps) appears.

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