Skip to main content
Glama
ask-aayan

ask-aayan

Availability

get_availability
Read-onlyIdempotent

Check a candidate's full-time start availability for a specific month by submitting a YYYY-MM date and receiving a yes/no answer.

Instructions

When he can start: current role, graduation date, and from when he is available full-time. Pass a month (YYYY-MM) to get a yes/no for that month, e.g. "2027-03" for March 2027.

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

Input Schema

NameRequiredDescriptionDefault
dateNoA start month in YYYY-MM form, e.g. "2027-03". Convert "March 2027" to "2027-03".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the description's job is to add output-shape context — which it does by disclosing that supplying a month switches the answer to a yes/no verdict for that month. It still doesn't state what a no-date call returns in full, but the added behavioral context is real.

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?

Two tight sentences with the core content front-loaded and the optional-mode explanation second. The YYYY-MM example restates the schema's own example verbatim, which is the only avoidable repetition.

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, no output schema, and annotations that already declare the read-only profile, the description supplies everything needed to call it correctly: the returned fields, the month mode, and the format. Nothing material is missing for a tool of this complexity.

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%, so the format and conversion rule are already documented; the description adds the semantic outcome of the parameter (a per-month yes/no answer) rather than just its syntax. The repeated "2027-03" example duplicates the schema, limiting the added value slightly.

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 the exact content returned — current role, graduation date, full-time availability start — plus the optional per-month yes/no mode, which is specific enough to separate it from siblings like get_experience or get_summary. It lacks an explicit verb ('retrieve'/'check'), but the resource and returned fields are unambiguous.

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?

Usage is only implied: an agent can infer that this tool answers 'when can he start' questions, and the second sentence explains the optional month mode. There is no stated when-to-use versus siblings (e.g., get_experience covers roles) and no when-not-to-use guidance.

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