Skip to main content
Glama

Get my scout application

get_scout_application
Read-only

The signed-in user's scout application: stage (none / researching / draft / pending_review / approved / declined), the drafted profile, what the research found, who invited them, and the next step. Free, read-only. Use it to resume an application, or when the user asks 'where is my scout application?'.

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_scout_application"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and 'Free, read-only' largely restates them. The description earns credit beyond that by disclosing the response payload in detail, including the full stage vocabulary (none through declined), which tells the agent what states to expect and that a 'none' stage is a valid no-application outcome.

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?

A single dense paragraph, front-loaded with the payload rather than preamble, with no wasted framing. The parenthetical stage list is long but functional; one could argue the 'Free, read-only' clause duplicates annotations and is the one expendable phrase.

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?

With no output schema, the description carries the burden of explaining return values, and it does so thoroughly, including the stage enum and 'next step' field. Minor gap: it does not state the exact shape when no application exists beyond the 'none' stage hint, nor whether fields are null in that case.

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?

The tool takes no parameters, so there is no parameter meaning to add; baseline for a zero-parameter tool applies. The description correctly makes clear that the subject is implicitly the signed-in user, which replaces what a user-id parameter would otherwise need to document.

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 opening clause names a specific resource and scope — 'The signed-in user's scout application' — and then enumerates exactly what that record contains (stage, drafted profile, research findings, inviter, next step). An agent can distinguish this from siblings like get_my_submissions or apply_as_scout without opening a schema.

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 two concrete triggers: resuming an application, and the natural-language question 'where is my scout application?'. It does not explicitly say when to prefer a different sibling (e.g., the submit or apply tools) for the mutation path, so the routing is clear but not complete.

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.