Skip to main content
Glama

local-mcp

by com.local-mcp

Web Find

web_find
Read-only

Finds elements on the current page of a web session so you can decide what to click or type into. query is a CSS selector OR visible text to match. Returns up to 30 matches with tag/text/name/type/href — never a silent empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesA CSS selector (e.g. 'input[name=q]') or visible text (e.g. 'Sign in').
sessionNoSession name (default 'default').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of matching elements (max 30 returned).
queryNo
matchesNoMatched elements with tag/text/name/type/href.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. Description adds useful behavioral context: always returns results (never a silent empty) and at most 30 matches. No contradictions. Could be more precise about empty match behavior but adequate.

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 concise sentences covering purpose, parameter usage, and output. No redundant information. Front-loaded with the core function. Every sentence 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?

Given that annotations cover safety and an output schema exists (though not fully shown), the description provides key functional details: query types, result limits, and field summary. It does not explain the session parameter default or behavior for non-existent sessions, but overall it is sufficiently complete for typical use.

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% so parameters are documented in schema. Description adds value by clarifying that query accepts both CSS selectors and visible text, and by summarizing the return fields (tag, text, name, type, href). This supplements the schema definitions effectively.

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?

Clearly states the tool finds elements on a web page, explicitly naming the verb (finds), resource (elements on current page), and purpose (to decide what to click or type into). Distinguishes from siblings like web_click and web_type by positioning itself as a precursor action. Also specifies output characteristics (up to 30 matches, fields returned, never silent empty).

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?

Implicitly guides when to use: before clicking or typing. Clearly explains that query can be a CSS selector or visible text. Does not explicitly state when not to use or mention alternatives like web_extract, but the context and sibling tool names provide natural differentiation. Lacks explicit exclusion criteria.

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

All local-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

Many tools are clearly distinct per app (e.g., chrome_*, safari_*, m365_*), but there is notable overlap between generic file tools like `file_list` and `finder_list`, both listing files; `search_contacts` and `list_contacts` serve similar purposes; `report_friction` and `report_problem` both send feedback to the team. The large number of tools with similar purposes in different domains creates moderate ambiguity for an agent.

Naming Consistency4/5

The naming convention is very consistent overall: most tools follow a `{app}_action` or `verb_noun` pattern (e.g., `chrome_click`, `create_calendar_event`, `list_reminders`). There are minor deviations like `lmcp_install_upgrade` (two verbs) and `complete_omnifocus_task` vs. `complete_reminder` (inconsistent verb placement). Still, the pattern is predictable and readable across the full set.

Tool Count2/5

With 225 tools, the surface is extremely large and heavy. While it covers many distinct domains (browsers, mail, calendar, files, notes, reminders, video editing, web automation, etc.), the sheer number makes it hard to navigate and likely includes many rarely-used tools. This is far beyond the well-scoped range of 3-15 tools and feels excessive even for a 'local everything' MCP server.

Completeness3/5

For many app integrations, the tool set provides solid CRUD coverage (e.g., Calendar has create, read, update, delete; Apple Notes has create, read, update, list, search; OmniFocus has create, list, search, complete). However, some areas are incomplete: for example, there is no tool to create a new Mail folder or delete notes. The 'web' tools lack a clear update/delete for saved sessions. The suite is broad but has notable gaps within individual domains.

Resources