Skip to main content
Glama
Sign In

PineBill

by app.pinebill
OverviewDiscussionsAdmin

Get project details

fetch_project
Read-onlyIdempotent

Fetch full details of a single project by ID. Returns all project data including description, status, budget, dates, customer, assignee, linked tasks, invoices, estimates, and expenses. Use this before updating a project to get current state, or when the user asks about a specific project's details.

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": {
      "id": "<id>"
    },
    "name": "fetch_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProject ID (from list_projects)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context by enumerating the returned fields and explaining that it retrieves current state, though it does not mention error behavior if the project is missing.

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 three sentences, front-loaded with the purpose, followed by the return contents and then usage guidance. Every sentence adds useful information without redundant phrasing.

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 one-parameter read tool with rich annotations and no output schema, the description is nearly complete: it explains what is returned and when to call it. It could mention what happens if the project is not found, but that is a minor gap for this tool.

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?

The single 'id' parameter is fully documented in the schema as 'Project ID (from list_projects)'. The description only restates that it fetches by ID and does not add format or validation details 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 states a specific verb and resource ('Fetch full details of a single project by ID') and enumerates the returned data, which clearly distinguishes it from create/update/delete project siblings and from broader listing tools.

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

Usage Guidelines4/5

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

It gives explicit usage contexts: before updating a project to get current state, or when the user asks about a specific project's details. It does not explicitly mention when to use list_projects for multiple projects or to discover an ID, though the schema notes the ID comes from list_projects.

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

All PineBill 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