Skip to main content
Glama
tearsheet

tearsheet

by kewonit

server_status

Read-only

Checks whether tearsheet is ready by reporting saved Tijori session status, local cache contents, and filing count; use it to diagnose missing data or failed tool calls offline.

Instructions

Report whether tearsheet is ready to use.

Shows whether a Tijori session is saved, what is in the local cache and how many filings the user has added. Call this first if another tool fails, or when the user asks why data is missing. It works offline and never contacts Tijori, so a saved session may still have been ended on Tijori's side. It returns no company data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds real value beyond that by disclosing it works offline, never contacts Tijori, and that a saved session may nonetheless have been ended server-side. It also warns it returns no company data, which prevents a common misuse. The one gap is that it does not describe the shape or fields of the status report, though the output schema likely covers that.

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?

Front-loaded with the core statement, then supporting caveats in descending importance; every sentence carries information an agent would act on. It is slightly longer than strictly necessary, and the block-indented formatting adds no structural benefit over a short paragraph.

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 zero-parameter read-only diagnostic with an output schema already defining return fields, the description covers what an agent needs: what it reports, when to call it, that it is offline, and the staleness caveat. Nothing material 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies, with no omissions to penalize.

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?

States a specific verb and resource: reports whether the tearsheet is ready, plus session-saved state, local cache contents, and filing count. That is clearly a local diagnostic/health tool, distinguishable from every sibling, which all fetch company or market data. The opening sentence ('ready to use') is slightly narrower than the fuller list that follows, which is the only thing keeping it from a 5.

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?

Gives two explicit triggers: 'Call this first if another tool fails' and 'when the user asks why data is missing.' That is concrete routing guidance rather than implied usage. It stops short of naming a specific sibling as an alternative or stating when not to call it, so it is not a full 5.

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