F
licenseA
qualityC
maintenanceLocal MCP server for managing arsnovasingers.org via the WordPress REST API, currently providing read-only audit tools for posts, pages, media, users, SEO, and site settings.
Last updated
89
updates
Server Details
Corduroy Labs studio updates over MCP: list_updates and get_update, backed by the site's JSON Feed.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.3/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
The two tools have clearly distinct purposes: one fetches a single update by slug, the other lists updates. There is no overlap or ambiguity.
Naming Consistency5/5
Both tools follow a consistent verb_noun pattern: get_update and list_updates. The naming is predictable and clear.
Tool Count4/5
With only two tools, the server feels slightly minimal but appropriate for a read-only blog update service. It could benefit from one or two more tools for searching or filtering, but the count is not unreasonable.
Completeness4/5
The server covers the basic read operations (list and get by slug) for blog updates. Missing are search, filtering by tags or date, and pagination beyond a limit parameter. However, for a read-only surface, the coverage is adequate.
Available Tools
2 toolsget_updateAInspect
Fetch one Corduroy Labs update in full by its slug.
Args:
slug: the update's slug (e.g. "the-studio-machine-readable").
Obtain slugs from list_updates().
Returns:
A dict with slug, title, url, date_published, summary,
content_html, and optionally tags, location, image.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Tool Definition Quality
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It describes the return format but does not explicitly state that the operation is read-only, nor does it mention side effects, authentication needs, or error cases. The lack of safety context reduces transparency.
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?
The description is concise, with two clear sections (Args, Returns) and no wasted text. The purpose is front-loaded in the first sentence. Every sentence adds value.
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 the simplicity of the tool (one parameter, no output schema, no annotations), the description covers purpose, parameter semantics, and return format. Missing are details on error handling or authentication, but for a fetch tool this is largely sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage for the slug parameter, so the description fully compensates by providing an example ('the-studio-machine-readable') and the source for obtaining slugs (list_updates()). This adds significant value 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?
The description clearly states the verb 'fetch' and the resource 'one Corduroy Labs update' with the identifier 'slug'. It distinctly separates from its sibling tool 'list_updates' by specifying 'in full' and the lookup mechanism.
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?
The description explains when to use: to get a full update by slug. It also instructs how to obtain slugs from list_updates(), implying a sequence. However, it does not explicitly state when not to use, such as for creating or listing updates.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_updatesAInspect
List Corduroy Labs blog updates, newest first.
Args:
limit: optional maximum number of items to return.
Returns:
A list of update summaries with: slug, title, url,
date_published, summary, and optionally tags, location, image.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| result | Yes |
Tool Definition Quality
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behaviors. It describes the output format and ordering, but does not mention potential pagination, rate limits, or error conditions. Adequate but not thorough.
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?
Concise with front-loaded purpose, followed by clear Args and Returns sections. No extraneous information.
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 low complexity (1 parametric, output schema exists), the description covers the input, output, and ordering. Missing details like default limit or maximum, but still functional.
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?
Only one parameter 'limit' with schema description coverage 0%. The description explains its purpose as 'optional maximum number of items to return', adding sufficient meaning 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?
States it lists blog updates newest first, clearly indicating the resource and action. The sibling tool 'get_update' implies this lists multiple, so differentiation is clear.
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?
Mentions ordering and optional limit, but lacks explicit guidance on when to use this tool vs the sibling 'get_update'. However, the context of listing vs single retrieval is implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceMCP RSS is a Model Context Protocol (MCP) server for interacting with RSS feedsLast updated928MIT
- AlicenseAqualityAmaintenanceMCP server for the Podcast Index API — search podcasts, track appearances, monitor trending shows, check feed healthLast updated18471MIT
- AlicenseAqualityAmaintenanceMCP server for publishing to WordPress. 13 tools cover posts, categories, tags, image hosting, featured images, and SEO metadata (Rank Math, etc.) One call runs the full markdown-to-live-URL pipeline.Last updated1362AGPL 3.0