Skip to main content
Glama

Cross-Team Search

cross_team_search
Read-onlyIdempotent

Search multiple configured team databases at once and return labeled results, so you can find context across teams without querying each database separately.

Instructions

Search across multiple configured team databases simultaneously. Returns results with team_db labels.

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

Input Schema

NameRequiredDescriptionDefault
tagsNo
limitNo
queryNo
sort_byNoSort results by timestamp (default) or importance scoretimestamp
end_dateNo
team_dbsNoSpecific team DB labels to search. Omit to search all configured DBs.
entry_typeNo
start_dateNo
fuzzy_matchNo
use_test_dbNo
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.
include_archivedNo

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
countNo
errorNoHuman-readable error message
errorsNo
detailsNoAdditional error context
entriesNo
successNo
categoryNoError category (validation, query, connection, internal)
degradedNo
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
searched_dbsNo
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv9.1.0
    • removedInput schema / properties / end_date / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
    • removedInput schema / properties / entry_type / enum
      Removed value: -[
      -  "personal_reflection",
      -  "project_decision",
      -  "technical_achievement",
      -  "bug_fix",
      -  "feature_implementation",
      -  "code_review",
      -  "meeting_notes",
      -  "learning",
      -  "research",
      -  "planning",
      -  "retrospective",
      -  "standup",
      -  "technical_note",
      -  "development_note",
      -  "enhancement",
      -  "milestone",
      -  "system_integration_test",
      -  "test_entry",
      -  "plan_draft",
      -  "adversarial_review",
      -  "plan_refinement",
      -  "plan_finalized",
      -  "copilot_validation",
      -  "other"
      -]
    • removedInput schema / properties / limit / maximum
      Removed value: -500
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +[
      +  "number",
      +  "string"
      +]
    • removedInput schema / properties / query / maxLength
      Removed value: -250
    • removedInput schema / properties / query / minLength
      Removed value: -1
    • removedInput schema / properties / sort_by / enum
      Removed value: -[
      -  "timestamp",
      -  "importance"
      -]
    • removedInput schema / properties / start_date / pattern
      Removed value: -"^\\d{4}-\\d{2}-\\d{2}$"
  2. First observedv9.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are tagged with team_db labels, which is genuinely useful output context, but says nothing about behavior when no DBs are configured, partial failures, or result merging/ordering across DBs.

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?

Two short sentences, front-loaded with the core action and scope. No wasted words, though the second sentence partly duplicates what the output schema already conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter federated search with an output schema present, the description is too thin: it omits how multiple DBs are combined, ordering, and the meaning of most parameters. The output schema relieves it of explaining return values, but the parameter and behavior gaps remain significant.

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

Parameters2/5

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

Schema description coverage is only 25% across 12 parameters, so the description carries a heavy burden and adds essentially nothing: it does not explain team_dbs selection, limit semantics, fuzzy_match, include_archived, or the workspace_id isolation caveat. Only the phrase 'configured team databases' loosely gestures at team_dbs.

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 ('Search across multiple configured team databases') and adds the distinguishing scope 'multiple' plus the team_db labeling of results. It is clear what the tool does, though it never names the single-DB sibling (team_search) it contrasts with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. With siblings like team_search, team_semantic_search, search_entries, and search_by_date_range, the agent must infer from the word 'multiple' that this is the federated variant; no alternative is named and no exclusion is stated.

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