Skip to main content
Glama

UseMyContext.ai

by io.github.usemycontext

Search (deep research)

search
Read-only

Search the user's files by filename and return matching documents in the deep-research result shape. ALIAS: this is the SAME search as search_files (same data, same permissions) - use it when your client requires the id/title/url search contract (ChatGPT deep research); otherwise prefer search_files for richer file metadata. Each result's id can be passed to fetch (or get_file) to read that document. Read-only; nothing is written, so it is safe to call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFilename query to match.
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
resultsYes

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. Added

TDQS

A5/5.0
Behavior5/5

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

The description aligns with annotations (readOnlyHint=true, destructiveHint=false) and adds useful behavioral context: it is the same search as search_files with the same permissions, is read-only, and returns result ids that can be passed to fetch or get_file. This goes beyond the structured annotations and clarifies side effects precisely.

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 primary purpose, then efficiently covers alias identity, invocation criteria, result usage, and safety in a few dense but relevant sentences. No filler or redundant restatement of the schema exists.

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 search tool with three parameters and an output schema, the description fully covers how to invoke it, when to prefer siblings, how scoping works, and what to do with results. Given the annotations and schema already present, nothing necessary for correct use is missing.

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

Parameters5/5

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

Although the schema already covers 100% of parameters, the description adds valuable semantic detail: handle takes precedence over projectId, both are honored only for account-wide connections, invalid handles are refused outright, and shared_context is the alternative for others' shared content. This meaningfully enriches the schema definitions.

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?

States a specific verb ('Search'), resource ('user's files'), and scope ('by filename'), and defines the output contract ('deep-research result shape'). It also distinguishes itself from search_files by explicitly labeling this the same search with a different result contract, so an agent can differentiate siblings immediately.

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?

Provides explicit when-to-use guidance: use this tool when the client requires the id/title/url search contract, otherwise prefer search_files for richer metadata. It also explains handle/projectId scoping behavior and directs shared-context access to shared_context, leaving no ambiguity about alternatives.

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