Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

projects_get

Retrieve a Project (Job) record by its ID to inspect Macola 10 project details and support lookups in MCP client workflows.

Instructions

Get the Project (Job) for a particular entry by specifying its ID.

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

Input Schema

NameRequiredDescriptionDefault
idYesProject/job ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden; 'Get' does imply a non-mutating read and it names what is returned (the Project/Job object). Missing are not-found/error behavior, any auth or permission requirements, and the exact return shape.

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?

One short sentence with the resource and lookup key front-loaded; nothing extraneous. 'By specifying its ID' is mildly redundant given the schema, which keeps it from a 5.

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 simple one-parameter getter with no output schema, the description covers what it fetches and by what key, which is close to sufficient. It leaves the relationship to 'projects_find' and failure behavior unspecified, so an agent may not know which of the two project tools to call.

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

Parameters4/5

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

There is a single parameter at 100% schema coverage, and the schema already defines 'id' as 'Project/job ID'. The description reinforces that the ID identifies the specific entry rather than filtering, which adds a small amount of meaning beyond the schema; baseline for full coverage is 3, and the single unambiguous parameter pushes it slightly higher.

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?

States a specific verb and resource ('Get the Project (Job)') scoped to a single entry by ID, so an agent can tell it is a single-record lookup. It does not differentiate itself from the sibling 'projects_find', which likely covers the same resource by other criteria.

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 only implied: the phrase 'for a particular entry by specifying its ID' suggests it is the exact-ID retrieval path as opposed to a search. No explicit when-to-use, when-not-to-use, or named alternative (e.g. projects_find) is given.

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