Skip to main content
Glama

Search Profile — Find Skills, Projects, Experience

search_profile
Read-only

Search personal profile content including bio, skills, projects, and social links to find specific keywords or information across your digital identity.

Instructions

Search across the entire personal profile for a keyword or phrase. Searches through: name, bio, job titles, companies, skill names, project names, article titles, book titles, social links, FAQ answers, and more. Returns matching fields with their location in the profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword to search for (e.g. 'TypeScript', 'open-source', 'running')

Implementation Reference

  • The core logic for searching the profile data.
    export function searchProfile(data: Record<string, unknown>, query: string): string[] {
      const results: string[] = [];
      const lowerQuery = query.toLowerCase();
    
      function searchObj(obj: unknown, path: string): void {
        if (typeof obj === "string") {
          if (obj.toLowerCase().includes(lowerQuery)) {
            results.push(`${path}: ${obj}`);
          }
        } else if (Array.isArray(obj)) {
          obj.forEach((item, i) => searchObj(item, `${path}[${i}]`));
        } else if (obj !== null && typeof obj === "object") {
          for (const [key, value] of Object.entries(obj as Record<string, unknown>)) {
            searchObj(value, path ? `${path}.${key}` : key);
          }
        }
      }
    
      searchObj(data, "");
      return results;
    }
  • src/server.ts:119-141 (registration)
    Registration of the search_profile tool in the MCP server.
    server.registerTool(
      "search_profile",
      {
        title: "Search Profile \u2014 Find Skills, Projects, Experience",
        description:
          "Search across the entire personal profile for a keyword or phrase. " +
          "Searches through: name, bio, job titles, companies, skill names, project names, article titles, book titles, social links, FAQ answers, and more. " +
          "Returns matching fields with their location in the profile.",
        inputSchema: z.object({
          query: z.string().describe("Keyword to search for (e.g. 'TypeScript', 'open-source', 'running')"),
        }),
        annotations: { readOnlyHint: true },
      },
      async ({ query }) => {
        const results = searchProfile(profile.data, query);
        const text =
          results.length > 0
            ? `Found ${results.length} match(es) for "${query}":\n\n${results.join("\n")}`
            : `No matches found for "${query}".`;
    
        return {
          content: [{ type: "text" as const, text }],
        };
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds value by specifying the scope ('entire personal profile') and what gets returned ('matching fields with their location'), but doesn't disclose behavioral traits like rate limits, auth needs, or pagination. No contradiction with annotations.

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 purpose, followed by specific searchable fields and return details. Every sentence adds value without redundancy, making it efficient and well-structured for quick understanding.

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?

Given the tool's low complexity (1 parameter, read-only), no output schema, and rich annotations, the description is mostly complete. It covers purpose, scope, and return format adequately, though it could benefit from more explicit usage guidelines or behavioral details like error handling.

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 description coverage is 100%, with the parameter 'query' well-documented in the schema. The description adds minimal semantics by listing examples of searchable content (e.g., 'TypeScript', 'open-source'), but doesn't provide additional syntax or format details beyond what the schema already covers.

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 clearly states the tool's purpose with specific verbs ('search across', 'find') and resources ('entire personal profile', 'matching fields with their location'). It distinguishes from the sibling 'ask_about_me' by focusing on keyword-based search rather than conversational querying.

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

Usage Guidelines3/5

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

The description implies usage context by listing searchable fields (e.g., 'skill names', 'project names'), suggesting when to use it for keyword lookups. However, it lacks explicit guidance on when not to use it or alternatives, such as how it differs from 'ask_about_me' in practice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/paladini/mcp-me'

If you have feedback or need assistance with the MCP directory API, please join our Discord server