Skip to main content
Glama
Sign In
ats-resume-writer

ats-resume-writer

by mutamiri-sudo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_access_info

Retrieve information about obtaining an access code (pay-what-you-want, $0 works), the rewrite engine, and current configuration. Use this to resolve missing or invalid access code errors.

Instructions

Get information about the ATS Resume Writer: how to obtain an access code (pay-what-you-want, $0 works), what the rewrite engine does, current configuration status, and the companion resume kit. Call this when rewrite_resume reports a missing or invalid access code.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool returns information about access code, rewrite engine, configuration, and kit. Since it's a read-only info tool, no destructive or auth details are needed, but it could mention the response format.

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 concise sentences, no fluff. Front-loaded with purpose and usage guidance.

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?

Given zero parameters and no output schema, the description thoroughly explains the tool's purpose and output. It also references the sibling tool for when to use it, making the context complete.

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

Parameters5/5

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

No parameters (0 params, 100% schema coverage). Description adds value by detailing what information is returned, compensating for lack of output schema.

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 description clearly identifies the tool as providing information about the ATS Resume Writer, specifically listing access code, rewrite engine, configuration, and companion resume kit. It distinguishes from sibling rewrite_resume by focusing on informational retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to call it: 'Call this when rewrite_resume reports a missing or invalid access code.' This gives clear context for use and differentiates from the sibling tool.

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