Skip to main content
Glama

DeepSearch

by app.deepsearch
OverviewDiscussionsAdmin

Build dossier

build_dossier
Read-only

Assemble one person's entire public footprint into a single sourced profile: identity, contact details, social accounts unified across platforms, work history, education, relatives, locations, and web mentions - every claim linked to the page it came from. Prefer this over reading search results yourself when you need the whole picture of one person rather than a single fact; it does the cross-platform correlation that a web search leaves to you. Pass a name plus the headline or username from search_people so the right individual is profiled. Repeat profiles are served from a shared cache: free and instant. Public sources only - never private accounts or breach data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe person's full name.
refreshNoRebuild from scratch instead of using the shared cache. Always meters.
headlineNoOptional descriptor to disambiguate, e.g. 'Engineer, London'.
usernameNoOptional known handle to focus the profile on the right person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / headline
      Added value: +{
+  "description": "Optional descriptor to disambiguate, e.g. 'Engineer, London'.",
+  "type": "string"
+}
    • changedInput schema / properties / name / description
      Previous value: -"The person's name, not a phone number, email, or handle."New value: +"The person's full name."
    • removedInput schema / properties / name / maxLength
      Removed value: -100
    • removedInput schema / properties / name / minLength
      Removed value: -2
    • removedInput schema / properties / profile_url
      Removed value: -{
-  "description": "The profileUrl of the professional source selected from search_people. Never infer account ownership.",
-  "maxLength": 400,
-  "type": "string"
-}
    • addedInput schema / properties / refresh
      Added value: +{
+  "description": "Rebuild from scratch instead of using the shared cache. Always meters.",
+  "type": "boolean"
+}
    • addedInput schema / properties / username
      Added value: +{
+  "description": "Optional known handle to focus the profile on the right person.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name",
-  "profile_url"
-]New value: +[
+  "name"
+]
  2. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / headline
      Removed value: -{
-  "description": "Optional descriptor to disambiguate, e.g. 'Engineer, London'.",
-  "type": "string"
-}
    • changedInput schema / properties / name / description
      Previous value: -"The person's full name."New value: +"The person's name, not a phone number, email, or handle."
    • addedInput schema / properties / name / maxLength
      Added value: +100
    • addedInput schema / properties / name / minLength
      Added value: +2
    • addedInput schema / properties / profile_url
      Added value: +{
+  "description": "The profileUrl of the professional source selected from search_people. Never infer account ownership.",
+  "maxLength": 400,
+  "type": "string"
+}
    • removedInput schema / properties / refresh
      Removed value: -{
-  "description": "Rebuild from scratch instead of using the shared cache. Always meters.",
-  "type": "boolean"
-}
    • removedInput schema / properties / username
      Removed value: -{
-  "description": "Optional known handle to focus the profile on the right person.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "profile_url"
+]
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds detail beyond the annotations by mentioning caching behavior ('Repeat profiles are served from a shared cache'), which is not present in the cached hints. It also outlines the types of data included ('social accounts', 'work history', etc.) and states what content is off-limits ('never private accounts or breach data'), providing a clear ethical boundary beyond what the readOnlyHint suggests.

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 concise yet comprehensive. It front-loads the core value proposition and distributes context across just two well-utilized sentences before getting to usage instructions. Every word is purposeful, whether defining scope, providing examples, or setting boundaries.

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?

Considering the tool's complexity and its small parameter set, the description effectively communicates the tool's role as a comprehensive alternative to search, and given the existence of a schema that defines the parameters, it doesn't need to list them in the tool description. The guidance on caching and suitable alternatives like 'ask_about_person' provides a complete understanding of when and how to use the tool.

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?

The schema provides descriptions for all 4 parameters, meeting the 100% coverage benchmark. While the description mentions the 'name' and the 'headline or username' parameters, it doesn't add extra semantic detail that the schema misses; it primarily reinforces what is already outlined 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?

Uses specific verbs like 'assemble' and 'build' to describe what the tool does, combined with a detailed resource ('one person's entire public footprint'). It clarifies the scope and distinguishes itself by specifying the cross-platform correlation of public data, setting it apart from sibling tools like search_people or ask_about_person.

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?

Explicitly states when to use this instead of 'reading search results yourself' and names an alternative, 'search_people'. It also provides precise input instructions on passing the 'headline or username from search_people', which is clear guidance for using the tool correctly.

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

All DeepSearch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources