statsSize and freshness of the whole index: companies, boards per ATS, open and total postings, events in the last 24 hours, and when the oldest active board was last crawled. Free. Use to tell a user how much coverage stands behind an answer, or to check the index is current before relying on it.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only operation (gathering stats) and mentions it is 'Free', which hints at no side effects or limitations. However, it does not explicitly state that it never modifies data, but the nature of the tool makes this clear enough.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise, using only two sentences to convey purpose, content, and usage. No unnecessary words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that the output schema exists and no parameters are present, the description provides all necessary context: it lists the specific metrics that will be returned and explains when to use it. It is self-contained and leaves no obvious gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is nothing to explain. The description adds no parameter-specific meaning, but no such meaning is needed. The schema coverage is automatically complete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that the tool provides size and freshness metrics for the entire index, enumerating specific data points (companies, boards per ATS, postings, events, crawl time). This distinguishes it from sibling tools that focus on individual companies or searches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly tells when to use the tool: to inform users about coverage behind an answer or to verify index freshness before relying on it. The word 'Free' also signals it has no cost or restrictions, adding practical guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct need: searching current postings, fetching one posting, listing a known company's roles, trend/count signals, incremental changes, and index stats. The descriptions explicitly call out the boundaries between overlapping tools (e.g., company_jobs vs. search_jobs, search_jobs vs. job_changes), so an agent can select the right one reliably.
Names are readable and mostly follow a noun-phrase style (company_jobs, job_changes, hiring_signal, stats), but get_job and search_jobs use a verb_noun pattern. The mix of verb-first and noun-first conventions is not chaotic, but it is inconsistent across a small set.
Six tools is well-scoped for a job postings index. Each tool earns its place, covering search, detail retrieval, company-level views, trend analytics, change feeds, and index health without redundancy.
The read-only domain is thoroughly covered: agents can search the market, fetch full postings, view a company's open roles, understand hiring trends, consume incremental changes, and verify data freshness. The workflow from search/company/changes to get_job has no dead ends.