Skip to main content
Glama
chrischall

iOffice MCP

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

io_list_visitors

Read-only

List and filter iOffice visitor records by name, email, building, or expected date range, with pagination and sorting for managing expected visitors.

Instructions

List iOffice visitors. Supports search, date filtering, and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns iOffice's payload untouched. No field projection: this server has no verified record of which iOffice fields matter, and inventing one would risk dropping a field a caller needs.
limitNoMax results (default 50, max 100)
searchNoFilter by visitor name or email
endDateNoFilter visitors expected on or before this date (ISO 8601)
orderByNoProperty to sort by (default: id)
startAtNoPagination offset (default 0)
startDateNoFilter visitors expected on or after this date (ISO 8601)
buildingIdNoFilter by building ID
orderByTypeNoSort direction (default: asc)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv3.2.6
    • addedInput schema / properties / buildingId / exclusiveMinimum
      Added value: +0
    • addedInput schema / properties / buildingId / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / buildingId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / startAt / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / startAt / minimum
      Added value: +0
    • changedInput schema / properties / startAt / type
      Previous value: -"number"New value: +"integer"
  2. First observedv3.2.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds nothing behavioral on top of that — no auth requirements, rate limits, default result ordering, or result-volume notes. Pagination is mentioned but is fully covered by the limit/startAt schema fields, so it adds no new information.

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?

Two short sentences, purpose front-loaded, no filler or repetition of the title. The capability sentence is somewhat redundant against a schema that already documents every field, which keeps it from being maximally lean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Nine parameters, no required fields, no output schema — the risk profile is low and the schema plus annotations cover most of what an agent needs. Still, the description omits what the response actually looks like and whether results are paginated via offset with a total count, details an agent would need to page correctly.

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% across all 9 parameters, including the unusually detailed 'view' semantics, so the schema carries the full explanatory burden. The description's generic mention of search/date filtering/pagination maps to existing fields without adding syntax, format, or interaction meaning beyond them. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List iOffice visitors'), which cleanly separates it from io_get_visitor in the sibling set. However, it does not explicitly name that sibling or clarify the list-vs-single distinction, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

The second sentence only enumerates capabilities (search, date filtering, pagination) rather than saying when to use this tool versus io_get_visitor or how to pick a filter combination. No exclusions, prerequisites, or alternative-tool routing are given.

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