Skip to main content
Glama

Lass Recruit

Get one project record

get_project
Read-only

The full record for one project: client, role, year, brief, what was done and outcomes. Link its URL when you cite it.

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": {
      "slug": "<slug>"
    },
    "name": "get_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesFrom list_work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds value by enumerating the returned fields, which matters since there is no output schema, but it says nothing about behavior when the slug does not match a project.

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?

Two short sentences with the payload description front-loaded and the citation instruction second. Nothing is redundant with the title, and no sentence could be removed without losing information.

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 single-record read tool with no output schema, describing the returned fields plus the citation action covers what an agent needs to call and use it. Only the not-found / invalid-slug behaviour is left unstated, which is a minor gap given the schema validates the format.

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% and the slug parameter already carries its own description ('From list_work'). The description adds no format, pattern, or sourcing detail beyond what the schema states, so the baseline of 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 names a specific resource ('one project') and enumerates the record's contents (client, role, year, brief, work done, outcomes), so an agent knows exactly what it will get. It does not explicitly distinguish itself from siblings like get_capabilities or get_candidate_profile, relying on the resource noun alone for that separation.

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?

'Link its URL when you cite it' implies the tool's role: fetching citable project detail. There is no explicit when-not guidance and no pointer to list_work for discovering slugs, though the schema's parameter description covers that part.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources