Skip to main content
Glama
Sign In
griasa

griasa

by Stari-am
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Context pack

get_context
Read-onlyIdempotent

Retrieve a person, project, or topic snapshot—open promises, recent meeting summaries, and the next meeting for a person—before answering questions about them.

Instructions

Everything Griasa knows about one person, project or topic, in one call and within a size budget: open promises in both directions (overdue first), recent meetings with their summaries, and for a person the next meeting with them. Use it before answering a question about someone or something; follow up with get_meeting or get_transcript only for detail it leaves out. When the budget is tight, the oldest meetings are left out first and omitted says how many.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "about": "<about>"
    },
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoperson, project or topic. Omit to let Griasa decide: a known person, then a project, then a topic.
aboutYesA person's name or email, a project name, or topic words.
budget_charsNoRoughly how much text to return. Default 12000, at most 40000.

Output Schema

NameRequiredDescriptionDefault
kindNo
foundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a safe, read-only, idempotent, non-destructive operation. The description adds important behavior beyond annotations: a size budget, oldest-meeting omission under pressure, and an `omitted` count that signals truncation.

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?

The description is front-loaded with the core value proposition, then moves cleanly to usage guidance and budget behavior. It is dense but every sentence contributes useful information.

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?

With an output schema present and rich annotations, the description fills the remaining gaps: what is returned, how to use it relative to siblings, and how truncation works under budget limits. An agent has enough information to call it correctly.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters are already documented in the schema. The description reinforces the entity scope and budget behavior but does not add much parameter-level detail beyond what the schema provides, making 3 the appropriate baseline.

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?

It names a specific resource and scope: everything known about one person, project, or topic, including promises, meetings, summaries, and next meeting. It also distinguishes itself from get_meeting and get_transcript as the broad first-look tool rather than a detail tool.

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?

The description explicitly says to use it before answering a question about someone or something, and it names get_meeting and get_transcript as follow-ups only when detail is missing. This gives clear when-to-use and alternative guidance.

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