Skip to main content
Glama
Sign In
selvin-search-mcp

selvin-search-mcp

by selvinchen97-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

plan_intent

Analyze user intent and create a search planning session. Required first step for structured search execution.

Instructions

Phase 1 of search planning: Analyze user intent. Call this FIRST to create a session.
Returns session_id for subsequent phases. Required flow:
plan_intent → plan_complexity → plan_sub_query(×N) → plan_search_term(×N) → plan_tool_mapping(×N) → plan_execution

Required phases depend on complexity: Level 1 = phases 1-3; Level 2 = phases 1-5; Level 3 = all 6.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "thought": "<thought>",
      "core_question": "<core_question>",
      "query_type": "<query_type>",
      "time_sensitivity": "<time_sensitivity>"
    },
    "name": "plan_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoSpecific domain if identifiable
thoughtYesReasoning for this phase
confidenceNoConfidence 0.0-1.0
query_typeYesfactual | comparative | exploratory | analytical
session_idNoEmpty for new session, or existing ID to revise
ambiguitiesNoComma-separated unresolved ambiguities
is_revisionNoTrue to overwrite existing intent
core_questionYesDistilled core question in one sentence
premise_validNoFalse if the question contains a flawed assumption
time_sensitivityYesrealtime | recent | historical | irrelevant
unverified_termsNoComma-separated external terms to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations are absent, so the description must carry the burden. It states it creates a session and returns session_id, but does not disclose side effects such as overwriting existing intent (though the is_revision parameter exists in the schema). The description doesn't mention idempotency, revision behavior, or any destructive implications. It's adequate but not fully transparent.

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 compact yet information-dense. It front-loads the purpose in the first sentence, then presents the pipeline flow and complexity rules in a clear, scannable format. There is zero redundancy; every sentence contributes necessary context.

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 role in a multi-phase pipeline, the description covers the essential context: it is the entry point, it returns session_id, and it specifies the full flow and complexity-based phase requirements. It does not address the revision use case (session_id revision) that the schema supports, but the schema covers that. Overall it is complete for the typical agent workflow.

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%, so the baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already documents. It doesn't mention any of the input fields (thought, core_question, query_type, etc.) or their roles. Thus it adds no extra value over 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 states the exact purpose: 'Phase 1 of search planning: Analyze user intent' and that it creates a session and returns session_id. It clearly differentiates from sibling tools by being explicitly 'FIRST' in the required flow, which is listed. This is specific and unambiguous.

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 explicitly says 'Call this FIRST to create a session' and provides the full required flow (plan_intent → plan_complexity → ...). It also gives conditional guidance based on complexity levels (Level 1, 2, 3), which tells the agent when to expect which subsequent phases. This is clear usage guidance with no ambiguity.

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