Skip to main content
Glama

Archlooks.com - Interior design and architecture gallery

Search architecture projects

search_projects
Read-only

Full-text search over the archlooks gallery (title, designer, city, country, category). Returns project ids — follow up with get_project_card for metadata or access_project (paid).

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": {
      "query": "<query>"
    },
    "name": "search_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, 1-25 (default 10)
queryYesSearch text, e.g. "hotel lobby" or designer name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior: the tool returns only project ids rather than full records, and one downstream path is paid — both facts that affect how an agent plans its calls.

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?

Two compact sentences: the first defines the search surface, the second defines the return shape and follow-up. Nothing is redundant and the most important fact (ids, not records) lands early.

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?

There is no output schema, so the description carries the burden of describing returns, and it does — project ids only — plus the two follow-up tools. For a two-parameter read-only search tool, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and documents both query and limit (1-25, default 10), so baseline would be 3. The description goes beyond the schema by naming the searchable fields, which tells the agent what kinds of query strings will actually match.

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?

States a specific verb and resource ('Full-text search over the archlooks gallery') and enumerates exactly which fields are searched (title, designer, city, country, category), so an agent knows precisely what this tool matches against.

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

Usage Guidelines4/5

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

Gives explicit follow-up routing: results are ids, so use get_project_card for metadata or access_project for paid access. It does not state when to prefer a different search tool, but the next-step path is unambiguous.

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.

Resources