Skip to main content
Glama

Search Industries

search_industries
Read-only

Lists the industries a company can be filed under. Match the user's description of their business against the list and offer the 3-5 closest entries. The one they pick, verbatim, is the industry save_company_details accepts; no other value is. Read-only; takes no arguments. Formation flow, in order: start_formation, create_checkout_session, verify_payment, save_company_details (industries from search_industries), submit_formation. Each response's nextStep is the step the flow now waits on.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Output Schema

NameRequiredDescriptionDefault
codeNoStructured error code when error=true (e.g. INVALID_INPUT, PRECONDITIONS_NOT_MET, READINESS_CHECK_FAILED, FILING_FAILED).
errorNotrue if the call failed
savedNoWhat this call saved.
messageNoHuman-readable status.
missingNoPrerequisites still unmet, in flow order. Empty when only filing remains.
nextStepNoThe step the formation flow now waits on; null once formation is complete.
companyIdNoThe company the call acted on.
companyNameNoName of the company the call acted on. Name it to the user.
nextQuestionNoThe customer-facing question for nextStep; null once formation is complete.
conversation_idNoThis conversation's handle. Pass it unchanged as conversation_id on every later call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedOutput schema / properties / message / description
      Previous value: -"Human-readable status or instruction."New value: +"Human-readable status."
    • removedOutput schema / properties / nextAction
      Removed value: -{
      -  "description": "Imperative for the agent — follow verbatim.",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / nextActionInput
      Removed value: -{
      -  "description": "{tool, arguments} template for the next call. Replace every <placeholder> in arguments with the user's real answer.",
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • changedOutput schema / properties / nextQuestion / description
      Previous value: -"Question to ask the user verbatim before the next call."New value: +"The customer-facing question for nextStep; null once formation is complete."
    • changedOutput schema / properties / nextStep / description
      Previous value: -"The tool to call next; null when the flow is complete."New value: +"The step the formation flow now waits on; null once formation is complete."
    • addedOutput schema / properties / nextStep / properties
      Added value: +{
      +  "description": {
      +    "description": "Where the customer stands at this step and what their options are.",
      +    "type": "string"
      +  },
      +  "missingFields": {
      +    "description": "Arguments of that tool the step still needs.",
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  "tool": {
      +    "description": "The tool that records this step.",
      +    "type": "string"
      +  }
      +}
    • changedOutput schema / properties / nextStep / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +[
      +  "object",
      +  "null"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / conversation_id
      Added value: +{
      +  "description": "This conversation's handle. Pass it unchanged as conversation_id on every later call.",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so "read-only; takes no arguments" mostly restates structured data. The description does add behavior the annotations cannot carry: the strict contract that only a verbatim returned value is valid, and the convention that each response's nextStep signals what the flow waits on.

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?

Front-loaded with the purpose, then the matching rule, then the constraint, then flow context — a sensible information hierarchy with no filler sentences. The formation-flow sentence is somewhat tangential to an industry lookup and could be trimmed, keeping it short of ideal.

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?

An output schema exists, so return values need no explanation. The description covers everything an agent must know to call and act on the tool: no arguments, what to do with the list, how to hand the chosen value downstream, and how to read nextStep.

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% and all three parameters are optional analytics fields already fully documented in the schema, so the baseline is 3. The description says "takes no arguments," which glosses the three analytics params but is not misleading since none affect the result; it adds no semantics beyond 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?

Opens with a specific verb+resource: "Lists the industries a company can be filed under." It also separates this lookup from every sibling by naming the field it feeds (`industry` for save_company_details), so an agent will not confuse it with save_company_details or list_companies.

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?

States exactly how to use the results: match the user's business description, offer the 3-5 closest entries, and have the user pick verbatim because no other value is accepted. It also places the call at a precise point in the formation flow, which is explicit when-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.