Skip to main content
Glama
Sign In

Pineprompt

by com.pineprompt
OverviewDiscussionsAdmin

Get Prompt Tool

get-prompt-tool
Read-onlyIdempotent

Fetch a single prompt by its numeric id. Optionally pass include to load the parent monitor/project/organization chain.

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": {
      "prompt_id": "<prompt_id>"
    },
    "name": "get-prompt-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoOptional comma-separated related resources to include in the response. Whitelisted: `monitor`, `monitor.project`, `monitor.project.organization`.
prompt_idYesThe numeric id of the prompt to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds one useful behavioral detail — that 'include' loads the parent monitor/project/organization chain — but says nothing about response shape, missing-id behavior, or permission requirements.

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?

Two sentences, zero wasted words, with the primary action front-loaded and the optional parameter mentioned second. It is appropriately sized for a simple read tool.

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 two-parameter read tool with complete schema coverage and rich annotations, the description covers the essential purpose and the one non-obvious parameter effect. A note on behavior for missing ids would make it fully complete, but nothing critical is absent.

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%, so both parameters are already fully documented in the schema, setting the baseline at 3. The description reinforces that 'include' loads the parent chain but adds no syntax, defaults, or constraints beyond what the schema's whitelist already provides.

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 states a specific verb and resource — 'Fetch a single prompt by its numeric id' — which is unambiguous and distinguishable from siblings like create-prompt-tool or update-prompt-tool. It does not explicitly contrast with a list operation, but the 'single prompt by id' framing is clear enough.

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?

Usage is implied: call this when you have a numeric prompt id. There is no explicit guidance on when to prefer this over other tools, no prerequisites, and no mention of error behavior when an id is missing. The optional 'include' parameter is described, which gives some usage context.

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

All Pineprompt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources