Skip to main content
Glama
prismeai

Prisme.ai MCP Plugin

Official
by prismeai

call_api

Send authenticated requests to any Prisme.ai REST API endpoint. Use for operations not available through dedicated tools, such as listing organizations or retrieving IAM context.

Instructions

Call any Prisme.ai REST API endpoint, authenticated server-side with the configured environment token (the token is NEVER exposed to the model). Use for endpoints not covered by a dedicated tool — e.g. list organizations ('/orgs'), the current IAM context ('/me'), org members, API keys, etc. path is relative to the environment apiUrl base, which already includes '/v2' (so pass '/orgs', not '/v2/orgs').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional JSON request body for POST/PATCH/PUT.
pathYesEndpoint path relative to the environment apiUrl base (which already ends in /v2). Examples: '/orgs', '/me', '/workspaces/<id>'. A leading slash is optional.
pickNoOptional field projection to keep responses small. Each named top-level key is kept; for list responses the projection is applied to every entry of `results`/`items` (or of a top-level array). E.g. ['slug','name'] on '/orgs'.
queryNoOptional query-string parameters, e.g. { limit: 200 }.
apiKeyNoAuthenticate with this key as `x-prismeai-api-key` (by default NO Bearer). For an `iak_<org>_…` org key the gateway resolves the org from the key with NO membership check — use this to create/publish an agent in an org you are not a member of (e.g. POST /workspaces/slug:agent-factory/webhooks/v1/agents).
methodNoHTTP method (GET, POST, PATCH, PUT, DELETE). Default: GET.
asSessionNoSend the token as the `access-token` cookie (browser-session auth) instead of a Bearer access token. Required for session-only endpoints like `PUT /user/active-org`; the active org set this way persists for subsequent asSession calls reusing the same token.
environmentNoEnvironment name (from PRISME_ENVIRONMENTS), e.g. 'sandbox' or 'prod'. Defaults to the default environment.
withUserBearerNoOnly with `apiKey`: ALSO send the configured user Bearer alongside the api key. Combines a real user identity (e.g. superadmin) with the org key's org context, so the gateway can take the admin/owner path while the key selects the org. Use to manage (read/update) an existing agent in another org.
Behavior4/5

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

Beyond the readOnlyHint=false annotation, the description adds critical behavioral context: the token is never exposed to the model, and it details authentication nuances for apiKey, asSession, and withUserBearer. It does not explicitly state that the tool can modify data, but that is implied by the annotation and the ability to use methods like POST.

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?

The description is a single, well-structured paragraph with no fluff. Every sentence serves a purpose, front-loading the core purpose and authentication before diving into parameter details. It efficiently handles 9 parameters.

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?

Given no output schema, the description could explain return format or error handling, but it does cover projection via 'pick'. For a generic API caller, this is largely sufficient, though a note on response structure would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds significant value by explaining path base, method defaults, optional leading slash, authentication details (apiKey vs asSession), and the interplay of withUserBearer. It clarifies security and parameter combinations beyond the schema.

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?

The description clearly states the tool calls any Prisme.ai REST API endpoint, with explicit mention that it's for endpoints not covered by dedicated tools. It distinguishes itself from sibling tools by listing examples like '/orgs' and '/me' that are not covered.

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?

It explicitly says to use for endpoints not covered by dedicated tools, giving concrete examples. It implies not to use when a dedicated tool exists, providing clear context and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prismeai/prismeai-mcp-debug'

If you have feedback or need assistance with the MCP directory API, please join our Discord server