Skip to main content
Glama

UseMyContext.ai

by io.github.usemycontext

Ask your documents

ask_docs
Read-only

Search the user's connected documents by MEANING and return the most relevant passages (the actual text), each cited with its source file, for you to read and quote. Use this to ANSWER a question from the user's documents - it returns grounded source content, not a file link, not a filename list, and not a pre-written answer (you do the reasoning). Before telling the user you do not know something about them or their work, search here first - the answer is often in their documents. Read-only; nothing is written, so it is safe to call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoHow many passages to return (default 12, max 50).
queryYesWhat to find in the user's documents (a question or topic).
handleNoOptional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given. Honored only for an account-wide connection; a single-project connection is already scoped and ignores it. A handle that is not one of the user's own profiles is refused outright, never quietly swapped for another profile. To read context someone ELSE shared with the user or published, use shared_context instead.
projectIdNoOptional: which of the user's projects to search - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
passagesYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / handle
      Added value: +{
+  "description": "Optional: name one of the user's OWN profiles by its public @handle (with or without the leading @), as listed by list_profiles - an alternative to projectId, and it takes precedence if both are given. Honored only for an account-wide connection; a single-project connection is already scoped and ignores it. A handle that is not one of the user's own profiles is refused outright, never quietly swapped for another profile. To read context someone ELSE shared with the user or published, use shared_context instead.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Optional: which of the user's projects to search - a projectId from list_profiles. Honored only for an account-wide connection; a single-project connection is already scoped and ignores this.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already carry readOnlyHint=true and destructiveHint=false, so the safety profile needs no disclosure; the description adds return behavior beyond them — grounded passages with source citations and the division of labor that the agent must do the reasoning. The line 'Read-only; nothing is written, so it is safe to call' restates the annotation rather than adding new behavioral information, which keeps this from a 5.

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?

Four sentences, with the core function and return contract front-loaded in the first sentence and the strongest usage directive (search before claiming ignorance) placed early. The final read-only sentence duplicates the annotations and is the only non-essential content, costing a point against an otherwise economical structure.

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 a full output schema, 100% parameter coverage, and read-only annotations, the description only needed to cover selection and invocation judgment, which it does thoroughly: what it returns, when to prefer it over claiming ignorance, and the reasoning obligation on the agent. Nothing an agent needs to decide whether to call this tool correctly 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?

All four parameters have rich schema descriptions (100% coverage), so the baseline is 3. The description adds one meaningful semantic layer beyond the schema: the query is interpreted 'by MEANING' rather than by keyword, which clarifies how to phrase the query parameter. It adds nothing about k, handle, or projectId, but those are already thoroughly documented in the 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 names a specific verb and resource ('Search the user's connected documents by MEANING') and a concrete return contract ('the most relevant passages... each cited with its source file'). It actively distinguishes itself from siblings with the negative clause 'not a file link, not a filename list, and not a pre-written answer,' which separates it from get_file, list_files, and the other search tools. The title 'Ask your documents' is vague on its own, but the description fully disambiguates it.

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?

It gives explicit when-to-use directives: 'Use this to ANSWER a question from the user's documents' and 'Before telling the user you do not know something about them or their work, search here first.' It states what it is not for ('not a file link, not a filename list... you do the reasoning') and the handle parameter names a concrete alternative ('use shared_context instead') for reading context someone else shared, routing the agent away from the wrong tool.

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

All UseMyContext.ai toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation3/5

Most tools have clear boundaries, but fetch/get_file and search/search_files are explicit aliases of each other, creating redundant purposes. account vs info and list_files vs search_files also require careful reading to tell apart, though the descriptions do provide guidance.

Naming Consistency3/5

The set mixes verb_noun names (list_files, query_table, suggest_update) with standalone nouns (account, info, profile) and bare verbs (fetch, search). The naming is readable and lowercase throughout, but the conventions are not uniform.

Tool Count5/5

Thirteen tools is a reasonable, well-scoped number for a personal-context and document-access server. The two alias pairs add some redundancy but do not make the set feel bloated.

Completeness4/5

The server covers the core read-only workflows: discovering files, searching semantically, querying tabular data, retrieving full documents, reading profiles, and accessing shared context. Direct profile editing or file mutations are intentionally out of scope for this read-only connection, and suggest_update provides the one sanctioned write path.

Resources