Skip to main content
Glama

Lass Recruit

Ryan Lasswell's profile and résumé

get_candidate_profile
Read-only

Start here. Returns Ryan Lasswell's title, availability, full résumé, skills, education, contact details, and notes on how the records are kept.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_candidate_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds scope information the annotations cannot: the payload includes personal contact details and "notes on how the records are kept," which signals both the sensitivity and the provenance of the data returned.

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 routing cue ("Start here") front-loaded ahead of the content list. Nothing is redundant with the title and every clause adds a distinct returned field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters and no output schema, the description carries the return-value burden itself and does so by enumerating the fields. For a tool this simple, an agent has everything needed to call it and to know what will come back.

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 are no parameters, so the baseline is 4 and no compensation is required. The description correctly avoids discussing inputs and instead spends its words on the returned content.

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?

Names a specific verb ("Returns") and enumerates exactly what the resource contains: title, availability, full résumé, skills, education, contact details, and record-keeping notes. That enumeration separates it cleanly from the sibling tools (capabilities, project, work list) without needing to name them.

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?

"Start here" gives a clear entry-point cue for an agent orienting itself before calling the other tools. It stops short of explicit when-not guidance or naming an alternative, but for a single zero-argument profile tool the implied usage is unambiguous.

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