Skip to main content
Glama

Embedding Status

localnest_embed_status
Read-onlyIdempotent

Check embedding backend status and verify vector-search readiness for local AI agents.

Instructions

Return active embedding backend/model status and vector-search readiness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaNo

Implementation Reference

  • The implementation of the `localnest_embed_status` tool, which fetches the vector index status and normalizes it using `normalizeEmbedStatus`.
    registerJsonTool(
      'localnest_embed_status',
      {
        title: 'Embedding Status',
        description: 'Return active embedding backend/model status and vector-search readiness.',
        inputSchema: {},
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
          idempotentHint: true,
          openWorldHint: false
        }
      },
      async () => {
        const status = vectorIndex.getStatus();
        return normalizeEmbedStatus(status);
      }
    );
Behavior4/5

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

Annotations cover safety profile (readOnly, idempotent, non-destructive). Description adds valuable domain context by specifying this checks 'active embedding backend/model' and 'vector-search readiness', indicating it verifies operational state of vector search capabilities.

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?

Single sentence with zero waste. Front-loaded with the action ('Return') and immediately specifies the scope ('embedding backend/model status'). Every word earns its place.

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?

Adequate for a simple status-checking tool with one optional parameter and existing output schema. Safety annotations are complete. Minor gap: could mention the response_format parameter to fully round out the contract, but sufficient for agent selection.

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 has 0% description coverage for the 'response_format' parameter, and the description text fails to compensate by explaining this parameter's purpose (controlling output format) or its default value ('json'). Agent must infer from schema alone.

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?

Description uses specific verb 'Return' with clear resources ('embedding backend/model status' and 'vector-search readiness'). Effectively distinguishes from sibling status tools like localnest_server_status or localnest_index_status by specifying the embedding-specific domain.

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?

Provides implicit differentiation through domain-specific terminology ('embedding', 'vector-search'), but lacks explicit guidance on when to prefer this over siblings like localnest_index_status or localnest_memory_status. No 'when-not-to-use' or alternative recommendations provided.

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/wmt-mobile/localnest'

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