Skip to main content
Glama
Sign In

OffLadder

by com.offladder
OverviewDiscussionsAdmin

Browse OffLadder's career guides by topic

browse_career_guides
Read-onlyIdempotent

Lists every OffLadder career guide on one subject, as questions with links, so someone can see what there is to read before picking one, e.g. 'show me everything on interviews', 'what guides do you have for students', 'reading list for after a layoff', 'what do you have on AI and jobs'. Shelves: stuck (Not sure what to do next), career-change (Changing careers), layoffs (After a layoff), ai (AI, jobs and the future of work), applying (CVs, resumes and applications), interviews (Interviews, offers and pay), students (Students, graduates and first jobs). Without a topic it lists the shelves with how many guides each holds.

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

Input Schema

NameRequiredDescriptionDefault
topicNoA shelf id such as 'applying' or 'layoffs', or a few words about the subject.

Output Schema

NameRequiredDescriptionDefault
topicNoThe shelf listed, or null for a free-text match.
guidesNo
shelvesNoEvery shelf, when no topic was given.
library_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds genuinely new behavior: results are presented as questions with links, and the zero-argument path returns the shelf list with per-shelf guide counts rather than an error.

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 core action and its output shape lead the description, the illustrative queries follow, and the shelf enumeration comes last as reference material. Every clause carries information an agent could otherwise get wrong, and there is no filler.

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?

For a single optional-parameter browse tool with a published output schema, the description covers the useful cases: what comes back with a topic, what comes back without one, and the full vocabulary of accepted topics. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100% and the topic parameter is optional, which gives a baseline of 3, but the description goes further by enumerating all seven valid shelf ids with their plain-language meanings and confirming that free-text subject phrases are also accepted. That is meaning the schema alone does not supply, since the schema offers only two example ids.

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 opens with a specific verb and resource ('Lists every OffLadder career guide on one subject') and states the shape of the result ('as questions with links'). It does not explicitly name how it differs from lookalike siblings such as find_career_guide or read_career_guide, so the differentiation is implied rather than stated.

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?

'so someone can see what there is to read before picking one' clearly positions this as the browse step preceding selection, and the sample phrasings ('show me everything on interviews') show the intended caller input. What's missing is an explicit pointer to the tool to call once a guide has been picked, or a stated boundary against find_career_guide.

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

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